CVE-2026-39210VulnerabilityPublished 7 Jun 2026

depthfirst's AI agent found 21 FFmpeg zero-days (CVE-2026-39210–39218) for ~$1,000 — oldest bug from 2003. What does this do to the economics of vuln research?

Source Reddit BlueTeam

Mentioned vulnerabilities

CVE-2026-39218

Not known to be exploited.

Data as of 7 Jun 2026, 02:48 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

FFmpeg maintainers have been responsive and are shipping fixes for the identified vulnerabilities. Users and organizations relying on FFmpeg should update to the latest patched versions as soon as they become available. Patch status is confirmed by the FFmpeg maintainers' response, but users should monitor official FFmpeg channels for the latest updates. No additional mitigation is specified beyond applying these official patches.

Discussion

An autonomous AI agent developed by the security startup depthfirst discovered 21 zero-day vulnerabilities in the FFmpeg multimedia framework, including nine assigned CVEs (CVE-2026-39210 through CVE-2026-39218). These vulnerabilities primarily involve heap and stack overflows in various parsers and demuxers, with some bugs dating back to 2003. FFmpeg maintainers have been responsive and are shipping fixes. The discovery raises concerns about the effectiveness of traditional static and dynamic analysis tools against memory corruption in large C codebases and the potential impact of AI-driven vulnerability discovery on disclosure pipelines and vulnerability economics.

r/blueteamsec (opens in a new tab)u/Expert_Sort74340 points0 comments

Posting this because I think it deserves more technical discussion than it's been getting.

depthfirst (a security startup) ran an autonomous AI agent against FFmpeg's ~1.5M lines of C. It returned 21 confirmed zero-days, each with a reproducible PoC. Nine CVEs assigned so far (CVE-2026-39210 through CVE-2026-39218). The rest are fixed but unnumbered. Total cost: approximately $1,000 for the run.

Most are heap or stack overflows in parsers and demuxers — TS demuxer, VP9 decoder, service-description-table parser (that last one dates to 2003, 23 years undetected). The FFmpeg maintainers have been responsive and fixes are shipping.

Technical concerns I'm sitting with:

If a startup can produce 21 PoCs for $1,000, what's the equivalent capability for a well-resourced threat actor running this at scale across hundreds of OSS projects simultaneously?
The 23-year dormancy issue — these bugs survived decades of fuzzing campaigns. What does that tell us about the fundamental limits of traditional SAST/DAST against memory corruption in C codebases?
Disclosure pipelines — the FFmpeg project is handling this well, but what happens when AI agents start generating hundreds of PoC disclosures per week across the ecosystem? The CVE numbering system is already slow.

I previously covered Microsoft's MDASH agentic AI system finding 16 Windows zero-days here if you want more background on the enterprise side of this trend: https://www.techgines.com/post/microsoft-mdash-agentic-ai-security-windows-vulnerabilities

Full writeup with CVE table and mitigation checklist: https://www.techgines.com/post/ai-agent-ffmpeg-zero-days-autonomous-vulnerability-discovery

Curious what people think, especially anyone who's worked on FFmpeg's codebase or on AI-assisted vuln research. Is the cost curve the thing we should be most focused on here?

Links cited in the discussion

Impact

The vulnerabilities are memory corruption issues (heap and stack overflows) that could potentially lead to security risks such as crashes or code execution if exploited. However, there are no known exploits in the wild at this time. The FFmpeg maintainers have released fixes, mitigating the risk. The discovery also signals a shift in vulnerability research economics, as AI can uncover multiple zero-days at low cost, potentially increasing the volume of disclosed vulnerabilities and challenging existing remediation workflows.

Summary

Depthfirst's AI agent autonomously analyzed FFmpeg's approximately 1.5 million lines of C code and identified 21 zero-day vulnerabilities, mostly heap or stack overflows in parsers and demuxers such as the TS demuxer, VP9 decoder, and service-description-table parser. Nine of these vulnerabilities have been assigned CVEs (CVE-2026-39210 to CVE-2026-39218), while the others have been fixed but remain unnumbered. The oldest discovered bug dates back to 2003, highlighting long-standing undetected issues despite extensive fuzzing efforts. FFmpeg maintainers have responded promptly with patches. This event illustrates the potential for AI to significantly reduce the cost and time of vulnerability discovery and raises questions about the scalability of current vulnerability disclosure and patching processes.

References

Community reviews

Loading reviews…