AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r... The same capabilities can help attackers: Epoch AI tested GLM 5.3 turning unshipped Firefox fixe...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: As of October 31, 2026, how is AI-driven vulnerability discovery transforming software security, including Palo Alto Networks’ discovery of. Article summary: As of October 31, 2026, AI-driven vulnerability discovery is making security research much faster, while shifting the bottleneck toward human validation, remediation and patch deployment—and creating opportunities to exp. Topic tags: general, general web, user generated, news, government. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermark
AI is changing software security at both ends of the process: it can help researchers find flaws faster, and it can help attackers use public clues to build exploits before fixes reach everyone. The central challenge is no longer discovery alone. Teams still need to verify findings, prepare fixes and get updates deployed.3
Palo Alto Networks told The Economic Times that AI helped identify more than 14,000 previously undetected open-source vulnerabilities and match a year’s worth of manual penetration-testing results in three weeks.19 That is a company-reported result, not an independently verified benchmark in the available evidence.
Anthropic’s figures illustrate why a higher discovery rate does not automatically mean more flaws have been confirmed or fixed. The company said its models found more than 29,000 candidate vulnerabilities over six months, while people had manually reviewed and triaged approximately 6,000. Those categories are different: a candidate is not necessarily a confirmed vulnerability, and a reviewed finding is not the same as an upstream patch.
Anthropic’s opt-in OSS Scanner offers eligible open-source projects free, recurring scans using its models, including Claude Mythos. Findings can reach participating maintainers without human review first. That approach may get potential issues in front of maintainers sooner, but it also makes the volume and quality of reports important. The available figures do not establish the exact October 2 totals or number of upstream fixes cited elsewhere.
Anthropic has said its human review capacity is a constraint, and TechTarget describes the scanner as shifting more of the vulnerability-processing burden to maintainers. Each useful finding may still need to be reproduced, assessed for impact, fixed, tested and released. Sending more reports is not the same as completing that work.
For projects with limited security capacity, a practical response is to prioritize reports that are reproducible and clearly explain affected code and impact. Organizations that depend on open-source software can also help fund the work of maintaining and securing it; the Electronic Frontier Foundation has specifically called for more support for open-source projects. The supplied evidence does not verify specific claims about maintainer burnout or particular projects’ staffing changes.
AI-assisted discovery has a defensive use, but security fixes can also reveal clues about the vulnerabilities they address. Epoch AI reported that GLM 5.3, an openly available model from Z.ai, used public but not-yet-shipped Firefox fixes to build working attacks against six Firefox releases. Epoch put the marginal cost at about $1,000 per successful attack.3
That was a controlled experiment, not evidence that the attacks were used against Firefox users. The report nevertheless demonstrates the risk of the patch gap: the interval between information about a fix becoming public and users receiving the update. Secondary reporting says Mozilla addressed a relevant flaw in Firefox 159.0.2
9
The implication is not that publishing fixes is unsafe; users need patches to protect themselves. Rather, defenders have to account for the possibility that technical details can be analyzed quickly, making prompt deployment especially important.3
October’s Microsoft Patch Tuesday shows why security totals should be read carefully. Microsoft’s release notes list 1,468 CVEs, while Veracode reports 1,413 vulnerabilities for the release; the available evidence does not reconcile the difference. Veracode also identifies an actively exploited Windows Shell security-feature bypass in the update. The count alone does not explain what caused the volume or how many issues were found with AI.
A separate example underscores the work involved in responding: CERT-EU says the PHP project announced two critical vulnerabilities on October 20 and released fixes the next day. Reuters reported that seven cybersecurity professionals warned that AI-discovered flaws could contribute to further disruption.17 That is a warning about potential consequences, not proof that AI discovery will always lead to an incident.
AI can help defenders find weaknesses earlier, but the Firefox experiment shows that exploit development can accelerate too.3 The sources available here do not establish which side will gain more overall. The clearest near-term priority is to connect discovery to effective triage and timely, widely deployed fixes—so that a growing stream of findings does not simply become a larger queue for maintainers and users.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r...
AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r... The same capabilities can help attackers: Epoch AI tested GLM 5.3 turning unshipped Firefox fixes into exploits for six releases at about $1,000 per successful attack, though the test does not show those attacks being...
AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r... The same capabilities can help attackers: Epoch AI tested GLM 5.3 turning unshipped Firefox fixe...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: As of October 31, 2026, how is AI-driven vulnerability discovery transforming software security, including Palo Alto Networks’ discovery of. Article summary: As of October 31, 2026, AI-driven vulnerability discovery is making security research much faster, while shifting the bottleneck toward human validation, remediation and patch deployment—and creating opportunities to exp. Topic tags: general, general web, user generated, news, government. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermark
AI is changing software security at both ends of the process: it can help researchers find flaws faster, and it can help attackers use public clues to build exploits before fixes reach everyone. The central challenge is no longer discovery alone. Teams still need to verify findings, prepare fixes and get updates deployed.3
Palo Alto Networks told The Economic Times that AI helped identify more than 14,000 previously undetected open-source vulnerabilities and match a year’s worth of manual penetration-testing results in three weeks.19 That is a company-reported result, not an independently verified benchmark in the available evidence.
Anthropic’s figures illustrate why a higher discovery rate does not automatically mean more flaws have been confirmed or fixed. The company said its models found more than 29,000 candidate vulnerabilities over six months, while people had manually reviewed and triaged approximately 6,000. Those categories are different: a candidate is not necessarily a confirmed vulnerability, and a reviewed finding is not the same as an upstream patch.
Anthropic’s opt-in OSS Scanner offers eligible open-source projects free, recurring scans using its models, including Claude Mythos. Findings can reach participating maintainers without human review first. That approach may get potential issues in front of maintainers sooner, but it also makes the volume and quality of reports important. The available figures do not establish the exact October 2 totals or number of upstream fixes cited elsewhere.
Anthropic has said its human review capacity is a constraint, and TechTarget describes the scanner as shifting more of the vulnerability-processing burden to maintainers. Each useful finding may still need to be reproduced, assessed for impact, fixed, tested and released. Sending more reports is not the same as completing that work.
For projects with limited security capacity, a practical response is to prioritize reports that are reproducible and clearly explain affected code and impact. Organizations that depend on open-source software can also help fund the work of maintaining and securing it; the Electronic Frontier Foundation has specifically called for more support for open-source projects. The supplied evidence does not verify specific claims about maintainer burnout or particular projects’ staffing changes.
AI-assisted discovery has a defensive use, but security fixes can also reveal clues about the vulnerabilities they address. Epoch AI reported that GLM 5.3, an openly available model from Z.ai, used public but not-yet-shipped Firefox fixes to build working attacks against six Firefox releases. Epoch put the marginal cost at about $1,000 per successful attack.3
That was a controlled experiment, not evidence that the attacks were used against Firefox users. The report nevertheless demonstrates the risk of the patch gap: the interval between information about a fix becoming public and users receiving the update. Secondary reporting says Mozilla addressed a relevant flaw in Firefox 159.0.2
9
The implication is not that publishing fixes is unsafe; users need patches to protect themselves. Rather, defenders have to account for the possibility that technical details can be analyzed quickly, making prompt deployment especially important.3
October’s Microsoft Patch Tuesday shows why security totals should be read carefully. Microsoft’s release notes list 1,468 CVEs, while Veracode reports 1,413 vulnerabilities for the release; the available evidence does not reconcile the difference. Veracode also identifies an actively exploited Windows Shell security-feature bypass in the update. The count alone does not explain what caused the volume or how many issues were found with AI.
A separate example underscores the work involved in responding: CERT-EU says the PHP project announced two critical vulnerabilities on October 20 and released fixes the next day. Reuters reported that seven cybersecurity professionals warned that AI-discovered flaws could contribute to further disruption.17 That is a warning about potential consequences, not proof that AI discovery will always lead to an incident.
AI can help defenders find weaknesses earlier, but the Firefox experiment shows that exploit development can accelerate too.3 The sources available here do not establish which side will gain more overall. The clearest near-term priority is to connect discovery to effective triage and timely, widely deployed fixes—so that a growing stream of findings does not simply become a larger queue for maintainers and users.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r...
AI is speeding up vulnerability discovery—from Palo Alto Networks’ reported 14,000 plus open source findings in three weeks to Anthropic’s more than 29,000 candidate vulnerabilities—but human validation and patching r... The same capabilities can help attackers: Epoch AI tested GLM 5.3 turning unshipped Firefox fixes into exploits for six releases at about $1,000 per successful attack, though the test does not show those attacks being...