Apple has introduced a cap on how many unresolved security reports a researcher can have open at once, along with a 30-day cool-down period once that limit is reached. These changes aim to reduce the flood of low-quality reports — especially those powered by AI — that strain its internal review process. Researchers can request a higher quota if they need it. Apple rolled this out in June.
What’s Behind the Changes
The surge in bug reports allegedly comes from growing use of large language models (LLMs) and other AI tools by researchers hunting vulnerabilities. While some AI-assisted submissions identify real issues, many are vague, duplicate, or poorly substantiated, adding burdens to Apple’s triage teams. The cap and cool-off aim to filter out noise and let genuine reports get proper attention.
One notable case involves Bynario, a security startup that used AI tools and filed over 50 reports on macOS in just three weeks. They uncovered a privilege-escalation chain — a serious exploit — but were prevented from submitting it once they hit the cap.
How Apple’s Bug Bounty Operates Now
The Apple Security Bounty program still offers up to $2 million for exploit chains that mimic sophisticated real-world attacks. With bonuses, that amount can exceed $5 million. Bonus payouts are available for bugs found in beta software or that bypass Lockdown Mode protections.
To qualify for those rewards, researchers should use Apple’s “Target Flags,” a system that objectively confirms what level of control the exploit achieves (such as register control, arbitrary read/write, or full code execution). Where Target Flags apply, submissions using them may even get rewarded before a full fix is released.
Also, the value of payouts for certain categories—like sandbox escapes or TCC permission bypasses—has dropped in many cases. Lesser vulnerabilities are now pulling in smaller nominal rewards, while Apple emphasizes payment for deeper exploit chains.
Importantly, although the cap limits how many open reports a researcher may have, Apple allows exceptions. If someone has a bug that truly demands attention, they can apply for increased quota so critical submissions don’t get blocked by procedural limits.
The 30-day cool-down kicks in once the researcher reaches their open-reports cap. After that period, they can submit new reports again — unless they’ve had to ask for and obtained a higher limit. Think of the cap as a throttle, not a blockade.
Apple made all this public following reporting by media outlets that highlighted how its internal security portal was being hit with massive numbers of reports, many of them questionable. The change was also framed as necessary to maintain the quality of its review pipeline.
These steps are the latest move in Apple’s broader adjustments to its bug bounty program. Past months have already seen softened payouts for common bugs and more rigorous requirements for proof of exploitability — all part of a mounting push toward higher-impact, deeply technical research.
Why it matters:As vulnerability discovery becomes easier via AI, companies like Apple must balance encouraging helpful security research with preventing overload from low-value submissions. For worthy researchers, relying on the quota-lift process and meeting the exploit chain and Target Flag criteria will be key to making sure serious bugs get through. Going forward, noting how Apple handles quota limits and verifying those procedural safeguards will be central for both researchers and users.
