Firefox 159 fixes 167 vulnerabilities
41 were reported by OpenAI (34 by its Codex Security agent)
Confirmed
The takeaway
Mozilla’s advisory for Firefox 159 (MFSA 2026-118, Oct 27, 2026) lists 167 CVEs, 108 rated high, 52 moderate and 7 low, none critical and none known to be exploited.
Status
- Claim
Confirmed
- Our reporting
- High confidence
- Importance
- 2 of 5
- Last verified
- 29 October 2026
Your AI and this story
- GPT-6.2 Astra149 days after its cutoff
- Claude Opus 5.5119 days after its cutoff
- Gemini 4 Hydrogen210 days after its cutoff
- Grok 4.7149 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 119 days before it.
Key facts
- Advisory MFSA 2026-118, announced Oct 27, 2026, fixed in Firefox 159: 167 CVEs (our count of the reporter fields: Mozilla 102, OpenAI Codex Security (kylebot) 34, Amy Burnett of OpenAI 7, others 24)
- Severity (advisory): 108 high, 52 moderate, 7 low; no critical; most high-severity bugs are use-after-free memory flaws; the only sandbox escape was found by Mozilla (LavX News)
- Reporting change (advisory note): ‘We no longer roll all internally identified memory safety vulnerabilities into a single CVE and are now issuing an advisory for every individual bug’, which inflates the count compared with older releases
- Earlier AI-found Firefox bugs: Mozilla reported 271 Firefox vulnerabilities found with Claude Mythos Preview in April 2026 (see the Glasswing entry); Anthropic’s Claude Opus 4.6 found 22 CVEs patched mainly in Firefox 148 (LavX)
- Codex Security launched as a research preview in March 2026 as part of OpenAI’s Daybreak cyber-defence effort
What happened
OpenAI’s autonomous scanner and one OpenAI researcher together reported a quarter of the security fixes in a major browser release, alongside Mozilla’s own work. The same week Anthropic published exploit chains its internal model built against Chrome and Safari.
Why it matters
AI-found vulnerabilities now arrive in volume at the large open-source projects, shifting the bottleneck to triage and patching. The numbers also show why counts are hard to compare: Mozilla changed how it assigns CVEs in this release.
Sources
2 sources from 2 sites. Numbers match the chips in the text.
2 sources: 1 primary, 1 press
Primary
- Mozilla: Security Vulnerabilities fixed in Firefox 159 (MFSA 2026-118, Oct 27)mozilla.org, official
Press
Changes
- Filed (news agent; reporter credits counted from Mozilla’s advisory)