CVE-2025-30403: Facebook mvfst · Heap-based Buffer Overflow
Affects Facebook mvfstSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jul 2025
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfacebook/mvfstpkg:github/facebook/mvfstOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately inventory their network infrastructure and applications to identify any use of mvfst, particularly versions prior to v2025.07.07.00. They should prioritize upgrading to the latest patched version of mvfst once available. Network administrators should implement strict filtering and monitoring of QUIC traffic, employing anomaly detection to identify suspicious or malformed QUIC packets that could exploit this vulnerability. Deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with updated signatures for QUIC protocol anomalies can help mitigate exploitation attempts. Organizations should also conduct penetration testing and fuzzing on their QUIC implementations to detect similar vulnerabilities proactively. Where possible, segment networks to limit exposure of vulnerable services and enforce strict access controls to reduce the attack surface. Finally, maintain up-to-date incident response plans to quickly address any exploitation attempts.
Description
A heap-buffer-overflow vulnerability is possible in mvfst via a specially crafted message during a QUIC session. This issue affects mvfst versions prior to v2025.07.07.00.