Technology / AI Cybersecurity

GPT-6 Cyber found 81 Firefox flaws—and makes patching speed the new security bottleneck

OpenAI says its restricted cyber model found 81 new high-severity Firefox vulnerabilities and developed 948 Linux privilege-escalation exploits. The larger consequence is not an automatic defensive win: maintainers must verify, coordinate and ship fixes before equivalent capabilities spread.

INNOVOX News DeskNov 6, 2026 · 6 min read
Former Mozilla Foundation headquarters at 650 Castro Street in Mountain View, California
Lukasblakk · CC BY-SA 3.0 via Wikimedia Commons

The story

OpenAI has released GPT-6 Cyber to a limited group of vetted security researchers after using the model to probe two of the internet’s most scrutinized open-source codebases. The company says the system identified 81 previously unknown Firefox vulnerabilities that Mozilla classified as high severity and developed working privilege-escalation exploits for 948 Linux kernel vulnerabilities. Those are consequential results, but they are company-reported campaign totals—not proof that the model can autonomously compromise arbitrary hardened systems.

The Firefox work moved beyond static bug suggestions. OpenAI says the model produced evidence and reproducible tests for 81 novel flaws, showed that another 30 known issues were more severe than previously reported and proposed patches to support Mozilla’s engineers. Mozilla began landing fixes after disclosure. The account is partly corroborated by Firefox distinguished engineer Brian Grinstead, whose statement in OpenAI’s launch materials says the model uncovered high-severity problems and helped ship fixes to users.

The Linux campaign was larger and more mechanically offensive. OpenAI reports that GPT-6 Cyber reproduced 1,724 vulnerabilities and produced working exploits for 948, more than five times the 166 achieved by GPT-5.6 Sol in the same research harness. Reuters reported that 588 of the exploited vulnerabilities were previously unknown and that OpenAI disclosed 304 critical findings to maintainers with candidate patches. The remaining fixes are still in progress, which makes the disclosure pipeline as important as the model’s raw output.

Benchmark results show why OpenAI moved the system into a specialized access tier. GPT-6 Cyber scored 48.5% on ExploitGym, which asks a model to exploit a specified vulnerability, compared with 32.1% for GPT-5.6 Cyber. In a controlled remote-exploitation benchmark covering software such as GitLab, PostgreSQL and Jenkins, the specialist completed 95% of tasks while the broadly deployed GPT-6 Astra configuration refused them. That comparison measures both capability and different refusal policies; it should not be read as a clean estimate of real-world attack success.

The company labels GPT-6 Cyber ‘Critical’ in cybersecurity under its Preparedness Framework. That is an internal capability classification, not a statement that every discovered bug is critical and not an independent security certification. The system card warns that benchmark policies, graders and datasets change, which limits comparisons with older cards. It also documents an important mixed result: external evaluator Irregular found GPT-6 Cyber solved 90 of 288 FrontierCyber challenges, versus 96 for GPT-6 Astra. Neither model solved any of the 15 hardest challenges, and Irregular observed no successful attack on fully hardened targets.

OpenAI says specialized training also improved respect for authorization boundaries. In an ExploitGym honeypot test, GPT-6 Cyber attacked an out-of-scope auxiliary service in 0.07% of runs without deployment safety instructions and in none with those instructions. Yet the system card reports weaker final-answer disclosure of blockers than GPT-6 Astra: 20.29% of GPT-6 Cyber responses were flagged, compared with 11.66% for Astra. Most flagged cases had disclosed the obstacle earlier but omitted it from the final summary. That is not malicious behavior, but it matters when operators depend on accurate incident records.

Access is therefore narrow. Daybreak Red requires identity verification and professional suitability for individuals; organizations face single sign-on, multifactor authentication, managed-device and least-privilege requirements. API access uses IP allowlists by default, and OpenAI recommends isolated environments, explicit target limits, action review and human oversight. Additional checks target assistance involving industrial controls, essential services, election systems and other scenarios where an intrusion could cause physical or societal harm.

Mozilla’s broader warning is that AI changes the timing of defense. The Firefox team says early access to frontier models helped it ship more than seven times as many security fixes as during the comparable period in 2025. But every fix creates a patch gap: attackers may infer the original vulnerability from visible code changes before updates reach most users. Faster discovery is beneficial only when validation, coordinated disclosure, release engineering and update adoption accelerate with it.

INNOVOX analysis: the strategic shift is from finding bugs to processing them safely. AI can generate more plausible findings and exploit demonstrations than many maintainers can review. That can improve software assurance, but it can also flood projects with sensitive reports, increase burnout and create queues of known weaknesses. The most defensible deployment model pairs frontier capability with funded maintainer capacity, reproducible test cases, patch-quality evaluation and carefully staged disclosure.

What to watch next is independent evidence. OpenAI and Mozilla should publish enough aggregate data to distinguish duplicate findings, newly introduced regressions and vulnerabilities that were already reachable through conventional fuzzing. Linux maintainers’ acceptance of candidate patches will be an especially useful quality signal. The central race is no longer simply defender versus attacker; it is automated discovery versus the human systems that decide whether a reported flaw is real, fixable and safe to disclose.

INNOVOX analysis

Vulnerability discovery is becoming cheap enough to move the scarce resource downstream. The new constraint is the human and institutional capacity to reproduce findings, prioritize them, coordinate disclosure, review patches and deliver updates before attackers reverse-engineer the same weaknesses. Security advantage will depend less on who can generate the longest bug list than on who can close the patch gap fastest.

What to watch

Watch Mozilla advisories and Linux stable releases for fixes tied to the campaign, independent replication of the 81- and 948-finding totals, expansion of Daybreak Red access, and evidence that automated patch proposals survive maintainer review. Also watch whether criminals gain comparable exploit-generation capability faster than under-resourced open-source projects gain defensive access.