CVE-2026-8047
Unauthenticated HTTP parsing flaw allows out-of-bounds write causing DoS.
Is CVE-2026-8047 being exploited?
Not confirmed. CVE-2026-8047 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-8047?
CVE-2026-8047 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-8047?
Yes. A fix has been recorded for CVE-2026-8047. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-8047 affect?
CVE-2026-8047 affects Unspecified devices with HTTP parsing component. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8047?
Monitor for patch; apply when released; implement input validation and rate-limiting.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can crash the device by sending crafted HTTP requests exploiting an out-of-bounds write.
Patch when possible
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected>= 4.15.0.0 and < 4.21.0.0
- affected< 4.21.0.0
- affected>= 3.5.21.0 and < 3.5.22.20
- affected>= 3.5.21.0 and < 3.5.22.20
- affected>= 3.5.21.0 and < 3.5.22.20
- affected>= 3.5.21.0 and < 3.5.22.20
- affected>= 3.5.21.0 and < 3.5.22.20
- affected>= 4.15.0.0 and < 4.21.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.