Skip to main content
VulnerabilityPublished

CVE-2025-6703: Mozilla neqo · Improper Input Validation

Affects Mozilla neqoSource CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/AU:Y/R:A/RE:L/U:Clear

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubmozilla/neqopkg:github/mozilla/neqoOther threatsAffected
  • =0.4.24
  • <=0.13.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade to a non-vulnerable version of Mozilla neqo as soon as a patched release becomes available. Monitor Mozilla's official channels for patch announcements.
  2. Implement network-level protections such as rate limiting and input validation proxies to filter malformed or suspicious QUIC/HTTP3 traffic that could trigger the vulnerability.
  3. Employ robust monitoring and alerting on services using neqo to detect crashes or abnormal behavior promptly, enabling rapid incident response.
  4. Conduct thorough testing of applications integrating neqo under various input scenarios to identify and mitigate potential crash triggers internally.
  5. Consider deploying fallback mechanisms or redundancy in network services to maintain availability in case of crashes.
  6. Engage with vendors or open-source communities using neqo to ensure timely updates and coordinated vulnerability management. These steps go beyond generic advice by focusing on proactive network filtering, monitoring, and fallback strategies tailored to the nature of the vulnerability and the neqo component's role in network communications.

Description

Improper Input Validation vulnerability in Mozilla neqo leads to an unexploitable crash..This issue affects neqo: from 0.4.24 through 0.13.2.

References

Community reviews

Loading reviews…