CVE-2026-55768
Unauthenticated WebSocket integer narrowing allows huge allocation crash in GoAccess
Is CVE-2026-55768 being exploited?
Not confirmed. CVE-2026-55768 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-55768?
CVE-2026-55768 is rated High. 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-55768?
Yes. A fix has been recorded for CVE-2026-55768. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55768 affect?
CVE-2026-55768 affects GoAccess < 1.11, GoAccess built-in WebSocket server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55768?
Upgrade to GoAccess 1.11+ or disable the WebSocket server immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can trigger ~18 exabyte allocation to crash GoAccess, causing remote denial of service.
Immediate action required
- affected< 1.11
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.