Is there a public exploit for CVE-2026-92693?

No public exploit for CVE-2026-92693 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-92693?

CVE-2026-92693 scores CVSS 8.2 (v3.1), rated high.

What does CVE-2026-92693 affect?

CVE-2026-92693 affects pavel-odintsov fastnetmon.

8.2 High

FastNetMon is a high-performance DDoS detector and sensor.

CVE-2026-92693

FastNetMon is a high-performance DDoS detector and sensor. In version 1.2.9 and earlier, parserawpackettosimplepacketfull() in src/simplepacketparserng.cpp dereferences ipv6extensionheaderfragmentt when IpProtocolNumberIPV6FRAG is present without first verifying that the eight-byte Fragment header remains. A crafted sFlow v5 RAWPACKETHEADER record can remotely reach this shared parser with the Fragment bytes omitted, causing an unauthenticated remote out-of-bounds read. The supplied harness detects the read under AddressSanitizer, but the advisory does not establish a production process crash. No fixed release is available as of this review.

Assessment

CVSS: 8.2 (v3.1)
Severity: High
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 5 November 2026
Last updated: 5 November 2026
Affected: pavel-odintsov · fastnetmon
Assigner: GitHub_M

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 8? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-92693