Apple Security Bounty Explained: Rewards Up to $2 Million and How It Works

The Apple Security Bounty pays security researchers who find and responsibly report vulnerabilities in Apple's software and services. It began as an invite-only program in 2016 and opened to all researchers in December 2019, with a top reward of $1 million. An overhaul that took effect in November 2025 doubled the top reward to $2 million for zero-click remote exploit chains, the kind used by commercial spyware. Bonuses can push total awards beyond $5 million. Reports go through Apple's Security Research site. You must follow Apple's rules: report privately, do not exploit the flaw against other people, and wait for a fix before going public. Apple reports it has paid more than $35 million to over 800 researchers since the program opened.

Ethan's son, now deep into a cybersecurity club at school, asked whether people really get paid millions for finding iPhone bugs, or whether that was just a headline. Ethan put him in touch with Jake, who has a friend working in security research. Jake explained it carefully: yes, the top rewards are real, but they are for extraordinarily rare, complex exploit chains found by experienced teams, and most rewards are far smaller. What matters for a beginner is how the system works, the rules that keep research legal, and the path from learning to reporting a first bug. This page lays out the program, the money, the rules and how people get started.

Reward amounts and rules change over time. Apple's Security Research site is the authoritative reference for current categories and terms; the figures here reflect the program as announced in 2025.

What a bug bounty is

A bug bounty is a reward a company pays to outside researchers who find security flaws and report them privately, giving the company a chance to fix them before criminals can exploit them. It turns a potential adversarial relationship into a cooperative one: researchers are paid for helping, rather than tempted to sell their findings elsewhere or publish them before a fix exists. Most large technology companies run bounty programs, either directly or through platforms that manage reports and payments.

Bounties sit within a wider practice called coordinated vulnerability disclosure: the finder reports privately, the vendor confirms and fixes the problem, and details are published once users are protected. Our page on the 2019 phone sensor fingerprinting attack is a good example: the researchers reported to Apple months before publishing, and Apple shipped a fix first.

Bounties also help companies prioritize: a steady flow of external reports shows where defenses are weakest and where engineering effort should go next.

How Apple's program evolved

The original version of this page reported the December 2019 opening, when Apple's program went from a small, private arrangement to one of the most generous public bounties in the industry.

Why Apple started later than others

Apple was one of the later large technology companies to launch a bounty: Google, Microsoft and Facebook had public programs years earlier. For a long time, Apple relied on internal teams and credited outside reporters in security notes without paying them, and researchers criticized the lack of rewards, pointing out that exploit brokers would pay well for the same flaws. The invite-only program of 2016 was a first step; the public opening in 2019 and the 2025 increases brought Apple to the top of the industry for its most critical categories.

The shift reflected a wider change in the industry: treating outside researchers as allies rather than threats, and recognizing that paying for bugs is far cheaper than suffering the attacks they enable.

Which products are covered

The program covers Apple's operating systems across iPhone, iPad, Mac, Apple Watch, Apple TV and Apple's newer platforms, along with iCloud and other Apple services, within the limits described in the terms. Some categories focus on particular attack surfaces, such as Safari's WebKit engine or wireless protocols. Third-party apps from the App Store are not covered, since they belong to their developers, who may run their own programs. Before spending time on research, check that the product, version and type of flaw are in scope; out-of-scope reports are still welcome for fixing but may not earn an award.

When in doubt about scope, asking through the program's contact channel before testing is better than guessing.

Mac security in the program

Macs were added to the bounty in the 2019 expansion, covering macOS flaws that bypass protections such as Gatekeeper, which checks downloaded apps, and the privacy controls that guard the camera, microphone and personal files. Mac malware has grown alongside Mac popularity, so these protections matter. Our page on what Gatekeeper does explains one of the defenses researchers test. For Mac users, the advice is the same as for iPhone: keep macOS updated and install apps from the App Store or identified developers.

Researchers studying Macs often begin with the privacy controls, since bypasses there are both impactful and well defined, making them a common first target for those new to Apple platforms.

What Apple pays for

Rewards depend on what the flaw lets an attacker do, how much user interaction it needs, and how reliable the exploit is. Apple's 2025 overhaul set the top categories roughly as follows:

• Zero-click remote exploit chains, which compromise a device with no action by the user: up to $2 million, the program's top award.
• One-click exploits, such as escaping Safari's WebKit sandbox, wireless proximity attacks, and attacks giving broad access to iCloud data: up to about $1 million.
• Bypasses of privacy protections, such as the controls that guard access to the camera, microphone and personal data: lower but substantial awards.
• Bonuses for flaws found in beta software before release, and for bypassing Lockdown Mode, Apple's hardened mode for people at high risk of targeted attacks, which can push totals beyond $5 million.

Most reports earn far less than the headline figures. Apple has said multiple individual payouts have reached $500,000, but the majority of awards are for less dramatic, still valuable findings. The top rewards target exactly the techniques mercenary spyware vendors use, which is why they are so high: Apple is competing with the price those vendors pay for the same flaws.

Exact amounts depend on the quality of the report and how complete the exploit is; Apple publishes detailed category descriptions on its Security Research site.

How reward amounts are decided

Across the industry, bounty amounts reflect a few factors. Impact comes first: what an attacker could do, such as read data, run code or take over an account, and to how many users. Then the conditions: whether user interaction is needed, whether the attacker must be nearby, and how reliable the exploit is. Report quality matters too: a complete, reproducible report with a working proof of concept earns more than a theoretical description. Many programs use severity scoring systems such as CVSS as a starting point, then apply their own reward tables, which Apple publishes on its research site.

Duplicates are a common disappointment: if someone else reported the same flaw first, the later report usually earns nothing, which is why speed and thoroughness both matter.

Why beta bugs earn a bonus

Apple pays extra for flaws found in beta versions of its software, before public release. A bug fixed during the beta never reaches the hundreds of millions of devices that would otherwise run it, so finding it early is worth more than finding it after release. The bonus also encourages researchers to study new features as soon as they appear, when they are most likely to contain fresh mistakes. For researchers, joining the developer or public beta programs on a spare device is the practical way to compete for these bonuses.

Researchers who test betas should still install them only on devices set aside for testing, since beta software can be unstable.

Apple's terms define exactly which beta findings qualify for the bonus, so check them before focusing on pre-release software.

Payment, taxes and charity

Awards are paid to the researcher, and in most countries they count as taxable income, so professional researchers keep records like any other freelance work. Apple has said it will consider matching awards that researchers choose to donate to charity, a gesture several companies have made to encourage giving. Researchers must meet eligibility rules, such as legal age requirements and not living in sanctioned countries; the program terms list them.

Payment typically follows once the fix is released and the award amount is confirmed, so there can be a gap of months between the report and the money arriving.

Researchers working through companies may have awards paid to their employer, depending on employment terms, which is worth clarifying before starting research as part of a job.

Target Flags: proving exploitability

A practical problem with high-value bounties is proving that a flaw is truly exploitable without building and deploying a full weapon. Apple's 2025 changes introduced Target Flags, a system that lets researchers demonstrate specific capabilities, such as achieving code execution or bypassing a privacy control, by retrieving a flag placed in a protected location, which Apple can verify automatically. It makes awards faster and more objective for the most important categories, and reduces back-and-forth over whether a bug "really" leads to a compromise.

For researchers, the change also means less time spent arguing about severity and more time on research, which makes the program more attractive compared with selling to brokers.

The approach mirrors capture-the-flag competitions, where retrieving a hidden flag proves a challenge was solved, which makes it familiar to the many researchers who learned that way.

How to report a vulnerability to Apple

1. Confirm the problem is a security issue, not an ordinary bug: it should let someone access data, run code or bypass a protection they should not.
2. Check that you tested only on your own devices and accounts.
3. Write a clear report: affected products and versions, steps to reproduce, the impact, and any proof of concept.
4. Submit it through Apple's Security Research site, signed in with your Apple Account.
5. Keep the details private while Apple investigates; the site shows the report's status.
6. Respond to Apple's questions, and wait for a fix and Apple's go-ahead before publishing anything.

Good reports are specific and reproducible. Apple, like most vendors, gives priority and better awards to reports that clearly show impact and include everything needed to reproduce the issue on a current version.

What happens after you report

After submission, Apple's security team triages the report, tries to reproduce the issue, and assesses its impact. The Security Research site shows the status as it moves through review, fix and award decisions. Complex issues can take weeks or months to fix properly, since a patch must work across many devices and versions without breaking anything. When a fix ships, Apple's security notes for that update typically credit the researcher, if they agree, and the award decision follows. Patience is part of the process; publishing early can disqualify a report and put users at risk.

If you disagree with a decision, such as a severity assessment, programs usually allow a polite follow-up with more evidence; clear, respectful communication tends to get the best results.

Found a security problem by accident?

Ordinary users sometimes stumble on security problems: a setting that exposes data it should not, or a lock screen that can be bypassed. You do not need to be a professional to report it. Write down what you did and what happened, avoid repeating it on anyone else's device or account, and report it through Apple's Security Research site or the vendor's security contact rather than posting it online. If unsure whether it is a security issue, reporting it privately is still the right call; the security team will decide.

Vendors generally appreciate these reports, and some programs reward them even when the finder is not a professional researcher.

Include the device model and software version in your report, since the security team will need them to reproduce what you saw.

Scams that misuse bug bounties

The popularity of bug bounties has attracted scams. Some people send small businesses vague, automated "vulnerability reports" about trivial issues and demand payment, a practice known as beg bounties. Others impersonate bounty programs to trick people into revealing login details. And some sites promise paid "bug hunting jobs" that are really fronts for fraud. Legitimate programs publish their rules openly, never ask for your passwords and pay through established channels. If you run a business and receive an unsolicited report, check whether it describes a real, specific problem before engaging, and never pay demands made under threat.

Researchers should also be wary of platforms or individuals offering to buy findings privately for cash; legitimate vendors pay through their own published programs.

Writing a report that gets taken seriously

1. Start with a one-sentence summary of the impact, such as which data an attacker can read.
2. List the exact devices, operating system versions and app versions tested.
3. Give numbered reproduction steps that someone else can follow without guessing.
4. Include a minimal proof of concept, recordings or logs that show the result.
5. Explain the security boundary crossed and why it matters to users.
6. Note anything you did not test, so the reviewer knows the limits.

Reviewers handle many reports, and the clearest ones are reproduced and rewarded fastest. A modest bug with a perfect report often fares better than a serious one described vaguely.

Keep a private copy of everything you submit; if you later need to clarify or follow up, having your exact wording and evidence to hand saves time.

The rules that keep research legal

Bug bounties come with conditions, and following them is what separates welcome research from illegal hacking. Typical rules include: test only on devices and accounts you own or have permission to use; do not access, modify or destroy other people's data; do not disrupt services; report privately to the vendor first; and do not publish details before a fix is available or the vendor agrees. Apple's terms also require that you be the first to report the issue and that the flaw affect a current, supported version.

Laws differ by country, and research that strays outside a program's rules may break computer misuse laws regardless of intentions. Reading the program terms carefully before starting is not a formality; it is the legal foundation of the work.

Safe harbor and the law

Many bounty programs include a safe harbor statement: a promise that the company will not pursue legal action against researchers who follow the program's rules in good faith. Governments have moved in the same direction. In 2022, the U.S. Department of Justice announced that it would not charge good-faith security research under the federal computer crime law, defining it as research done to test, investigate or fix security flaws without causing harm. These protections only apply when you stay within the rules; accessing other people's data or demanding payment falls outside them. Researchers outside the United States should check their own country's laws, which vary.

Keeping records of your testing, including dates and the accounts and devices used, helps show good faith if questions ever arise.

Bounties versus the exploit market

A researcher who finds a serious flaw has a choice. Reporting it to the vendor earns a bounty and public credit and protects users. Selling it to an exploit broker may pay more for the rarest bugs, but the buyer's customers may use it to spy on people. Bounty programs, legal frameworks and professional ethics all push toward reporting, and most researchers choose it. Apple's 2025 increases were explicitly aimed at narrowing the financial gap for the most dangerous categories, so the ethical choice is also a well-paid one.

Broker prices are also unreliable for sellers: payments may be staged and canceled if the flaw is patched, and sellers have no control over how the exploit is used.

Some countries have tightened rules on selling hacking tools, adding legal risk to the broker route on top of the ethical concerns.

Do bug bounties work?

Bug bounties have clear benefits: they bring thousands of skilled eyes to a company's products, reward people for doing the right thing, and create a legal path for research that might otherwise happen in the shadows. They also have limits. Payouts can be slow or disputed, scope rules can exclude important areas, and large programs receive many low-quality reports that need sorting. Bounties complement, rather than replace, a company's own security engineering and internal testing. Overall, the industry consensus is that well-run programs make products safer, which is why they have become standard practice.

For users, the best evidence is in the security notes: long lists of credited researchers in each update show the model working month after month.

Companies that publish statistics on their programs, as Apple did with its payout totals, make it easier for researchers and the public to judge how well they work.

What the bounty means for ordinary users

For people who simply use iPhones, iPads and Macs, the bounty's value is indirect but real: more flaws found by friendly researchers means more flaws fixed before criminals or spyware vendors can use them. Those fixes arrive in software updates, often with notes crediting the researchers. The practical takeaway is to install updates promptly, including the quick security responses Apple sometimes delivers between full updates. Our guide to updating an iPad covers the process, which is the same idea on iPhone.

People at elevated risk of targeted attacks, such as journalists, activists and executives, can also turn on Lockdown Mode in Privacy & Security settings, which disables many features attackers exploit, at the cost of some convenience.

Lockdown Mode is free and built in; there is no paid security app that offers the same protection on an iPhone.

How fixes reach your devices

When Apple fixes a reported vulnerability, the fix ships in a software update: a full version update, a point release, or a smaller, faster security update that Apple can deliver between regular releases and that may need only a quick restart. Each update's security notes, published on Apple's support site, list the vulnerabilities fixed with their identifiers and, where the researcher agrees, credit them by name. Turning on automatic updates, including the security response option in Software Update settings, means these fixes reach you without any effort, often within days of release.

Older devices that no longer get major updates may still receive some security fixes for a while, which is another reason to install whatever updates are offered.

When an update is marked as fixing an actively exploited vulnerability, install it the same day; those are the flaws attackers are already using.

Lockdown Mode in more detail

Lockdown Mode, available on iPhone, iPad and Mac, is designed for the small number of people who may be personally targeted by sophisticated attacks. When on, it blocks most message attachments other than images and disables link previews, turns off certain complex web technologies unless a site is excluded, blocks incoming FaceTime calls from people you have not called before, blocks wired connections to computers when the device is locked, and prevents installing configuration profiles. Turn it on in Settings > Privacy & Security > Lockdown Mode. Most people do not need it, but for journalists, activists and others facing state-level threats, it closes many of the doors zero-click exploits use, which is why bypassing it earns a bounty bonus.

You can exclude trusted websites from Lockdown Mode's web restrictions if a site you rely on stops working, keeping most of the protection while restoring the sites you need.

Memory safety and the future of exploits

Many of the most valuable exploits rely on memory corruption bugs, where software reads or writes memory it should not. Apple and others are attacking the problem at its root: writing new code in memory-safe languages such as Swift, adding hardware features that detect memory misuse, and isolating risky processing in tightly controlled sandboxes. Apple's newest chips include memory integrity protections designed to stop many such bugs from being exploitable at all. As these defenses spread, exploits become harder and rarer, which is another reason rewards for the remaining ones keep rising.

Defenses also make the remaining exploits more complex, often requiring several chained flaws, which is why top rewards are for complete chains rather than single bugs.

Rust and Swift adoption across the industry is part of the same trend, steadily shrinking the class of bugs that once dominated exploit chains.

Why zero-click exploits are worth so much

A zero-click exploit compromises a device without the victim clicking anything, often through a message or data the phone processes automatically. Such exploits have been used by commercial spyware sold to governments to target journalists, activists and politicians, as investigations into tools like Pegasus have shown. Because they are silent and hard to defend against, they are extremely valuable to attackers, and brokers have offered large sums for them. Apple's top bounty rewards are set to compete with that market, so that a researcher who finds such a chain has a strong legitimate reason to report it.

Apple has also built defenses aimed at these attacks, including Lockdown Mode and, on its newest hardware, memory safety protections designed to make the memory corruption bugs behind many exploits much harder to use.

Could your phone be targeted?

For the vast majority of people, zero-click spyware is not a realistic threat: such exploits are expensive and used against a small number of high-value targets. Apple sends threat notifications by email and in the Apple Account to users it believes may have been targeted by state-sponsored attackers, with advice on next steps. If you receive one, take it seriously: turn on Lockdown Mode, update all devices, and contact a specialist organization that helps civil society with digital security. Everyone else is best served by the basics: updates, a strong passcode and caution with unexpected links.

Real Apple threat notifications never ask you to click links, open files, install apps or share passwords, so a message claiming to be a threat notification that does any of these is itself a scam.

Notable exploits that shaped the program

Several real-world attack chains show why Apple raised its rewards. In 2021, researchers at the Citizen Lab found FORCEDENTRY, a zero-click iMessage exploit used to install the Pegasus spyware, which Apple patched in iOS 14.8. In 2023, BLASTPASS, another zero-click chain delivered through image attachments, was found in use and fixed in an emergency update. The same year, the security firm Kaspersky disclosed Operation Triangulation, a sophisticated zero-click campaign against iPhones. Each was discovered after being used against real people; bounties aim to get such flaws reported before that happens.

Each of these episodes ended with an emergency update and a public warning to install it, a reminder that the fastest protection for users is updating as soon as security fixes are released.

Investigations by groups such as the Citizen Lab and Amnesty International's security lab have been central to uncovering these campaigns, often by examining the phones of people who suspected they were targeted.

How Apple's program compares

Apple is not alone. Google runs vulnerability reward programs covering Android, Chrome and its cloud services; Microsoft pays bounties across Windows, Microsoft 365, Azure and more; and many companies use platforms such as HackerOne and Bugcrowd to manage public programs. Top rewards vary widely, with Apple's among the highest for its most critical categories. Programs also differ in scope, speed of response and payment terms, which researchers weigh when deciding where to focus.

Researchers often specialize in one ecosystem, since the deep knowledge needed to find serious flaws in a platform takes years to build and transfers only partly to others.

Comparing headline maximums can mislead, since what matters to researchers is the realistic award for the kinds of flaws they actually find, along with the speed and fairness of the process.

Public and private programs

Some bounty programs are public, open to anyone who follows the rules, like Apple's since 2019. Others are private, invitation-only programs where companies invite researchers with proven track records, as Apple's was from 2016. Private programs reduce noise from low-quality reports and let companies test new products quietly, while public programs reach a wider pool of talent. Many researchers build reputations on public platforms and then receive invitations to private programs, which often have less competition and higher rewards.

Apple's history shows both models: the private phase let it build processes with trusted researchers, and the public phase widened the net once those processes were ready.

Platforms that host bounty programs publish leaderboards and reputation scores, which help researchers earn invitations to private programs over time.

If you run a website or product

Companies of any size can benefit from the same idea without a big budget. Publishing a security.txt file, a small text file at a standard location on a website that tells researchers how to report problems, is a simple first step. A clear vulnerability disclosure policy, promising not to pursue legal action against good-faith researchers who follow it, encourages people to report rather than ignore or publish problems. Paid bounties can follow later, often through a bounty platform that handles triage.

Even a simple monitored email address such as security@ your domain, mentioned in the website footer, means a researcher who finds a problem knows where to send it.

Thanking reporters publicly, with their permission, costs nothing and builds goodwill in the research community, which encourages more people to report rather than stay silent.

How beginners get started in security research

The headline millions are for elite teams with years of experience, but the path into security research is open. Most people start by learning networking, operating systems and programming, then web security, where many bounty programs accept beginner-friendly reports. Practice platforms with legal, intentionally vulnerable labs and capture-the-flag competitions build skills safely. Tools commonly used in learning environments run on Linux distributions such as Kali; our guide to installing Kali Linux in VirtualBox sets up a safe practice machine.

Ethan's son's club now spends Friday afternoons on legal practice labs. Jake's advice to them was the same every security professional gives: learn on systems you are allowed to break, read program rules before testing anything real, and value a well-written report as much as a clever finding.

Questions parents ask

Parents of teenagers drawn to cybersecurity often worry it is a path to trouble. Done properly, it is the opposite: a respected, well-paid field built on rules, permission and ethics. Encourage learning through school clubs, structured courses and legal competitions; make clear that testing systems without permission is off limits, whatever the intention; and look for mentors through school or local security groups. Ethan's main question for Jake was whether his son could get into legal trouble. The answer was simple: not by practicing on labs designed for it and following program rules, which is exactly how professionals train.

Many universities and employers now actively recruit students with capture-the-flag experience, so the hobby can open real doors.

Setting up a separate practice computer or virtual machine at home, away from family devices, is a simple way to support the hobby safely.

Apple's resources for researchers

Apple publishes material that helps researchers understand its systems: the Apple Platform Security guide, which explains how hardware and software security features work; the Security Research site, with program rules, categories and blog posts about its defenses; and security notes for every update, listing fixed vulnerabilities and credited researchers. Reading recent security notes is a good way to see what kinds of flaws are being found and fixed, and which areas of the system attract the most research.

Conference talks by security researchers, many posted online free, are another rich source; they explain how past flaws were found and fixed, often in more accessible language than technical papers.

Reading the guide is also worthwhile for ordinary curious users, since it explains in plain terms how features like encryption, Face ID and app sandboxing protect data.

Security research as a career

Bug bounty hunting can be a part-time income or, for a few, a full-time career, but most security researchers work in salaried roles: penetration testers, vulnerability researchers, security engineers and incident responders. Bounty findings make strong portfolio pieces when applying for these roles, since they show real impact and clear communication. Certifications, university courses and open-source contributions also help. The field rewards curiosity, persistence and careful writing as much as technical brilliance.

Young people interested in the field can find school clubs, online courses and capture-the-flag competitions aimed at beginners, many of them free.

Communication skills matter as much as technical ones: explaining a flaw clearly to developers and managers is half the job.

Salaries in the field are generally strong and demand outstrips supply in many countries, which makes the patient learning path a sound investment.

A beginner's roadmap

1. Learn the basics of networking, operating systems and one programming language.
2. Study common web vulnerabilities through free, legal training resources.
3. Practice on intentionally vulnerable labs and capture-the-flag challenges.
4. Read public bug bounty reports and security notes to see real findings.
5. Start with beginner-friendly public bounty programs, following their rules exactly.
6. Write up your learning, building a portfolio of reports and write-ups.

Most researchers spend months or years before their first significant finding; persistence and careful reading of documentation matter more than any single tool.

A dedicated practice machine, such as a virtual machine with security tools, keeps experiments separate from the computer you use for banking and schoolwork.

Joining a community, such as a local security meetup or an online forum for beginners, makes the learning faster and keeps it on the right side of the rules.

Jailbreaks, bounties and the gray market

Some of the same flaws that earn bounties have historically been used for jailbreaks, which remove iOS restrictions so users can run unapproved software. Jailbreaking communities often publish exploits openly, which helps users but also means the flaws are known to attackers until patched. Our page on jailbreaking iOS today explains the trade-offs. There is also a gray market where brokers buy exploits to resell to governments or companies; bounties exist partly to keep researchers away from it by offering legitimate, legal rewards.

For ordinary users, the safest position is simple: keep devices updated and avoid installing tools that rely on unpatched flaws, whatever they promise.

Jailbroken devices also lose some of the protections that make zero-click attacks hard, which is one reason security-conscious users avoid them.

What this page said in 2019

When this page was first written in December 2019, Apple had just opened its bug bounty to the public, with rewards up to $1 million. Six years on, the program has paid tens of millions of dollars, doubled its top reward and introduced tools to verify exploits more objectively. This rewrite updates the figures and adds the context: how the program works, the rules, and what it means for everyone else.

The direction of travel is clear: higher rewards for the most dangerous flaws, better tools for researchers, and a public program that treats outside researchers as partners.

Apple Security Bounty: frequently asked questions

Ethan's son has not found a million-dollar bug, and Jake told him not to expect to. But he has found small flaws in practice labs, written clear reports about them, and learned that the rules matter as much as the skills. Somewhere, people like him will grow into the researchers whose quiet reports become the security notes in next month's update. That is the real point of a bug bounty: turning curiosity into protection for everyone.

Revision note. Written October 2, 2026, rewriting our 2019 note on Apple opening its bug bounty to the public into a complete guide to the Apple Security Bounty, its rewards, rules and meaning for users. May every flaw be found by someone who reports it.