How severe is CVE-2026-55768?

CVE-2026-55768 has a CVSS 4.0 base score of 8.7, rated high severity.

Is CVE-2026-55768 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-55768?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-55768 published?

CVE-2026-55768 was published on 2026-07-30 and last updated on 2026-07-31.

CVE-2026-55768

CVE-2026-55768 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-681.

Key facts

Severity: High (CVSS 4.0 base score 8.7)
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-681
Published: 2026-07-30
Last modified: 2026-07-31

Description

GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. Prior to version 1.11, the built-in WebSocket server narrows a 64-bit extended frame length into the signed 32-bit WSFrame.payloadlen field before enforcing the maximum frame size, allowing an unauthenticated remote client to bypass the guard and force an approximately 18-exabyte allocation request that terminates the process. This issue is fixed in version 1.11.

Frequently asked questions

What is CVE-2026-55768?: GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. Prior to version 1.11, the built-in WebSocket server narrows a 64-bit extended frame length into the signed 32-bit WSFrame.payloadlen field before enforcing the maximum frame size, allowing an unauthenticated remote client to bypass the guard and force an approximately 18-exabyte allocation request that terminates the process. This issue is fixed in version 1.11.
How severe is CVE-2026-55768?: CVE-2026-55768 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2026-55768 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-55768?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-55768 published?: CVE-2026-55768 was published on 2026-07-30 and last updated on 2026-07-31.

References

Other CWE-681 vulnerabilities

CVE-2022-40138 — Critical (CVSS 9.8): An integer conversion error in Hermes bytecode generation, prior to commit 6aa825e480d48127b480b08d13adf70033237097,…
CVE-2021-36357 — Critical (CVSS 9.8): An issue was discovered in OpenPOWER 2.6 firmware. unpack_timestamp() calls le32_to_cpu() for endian conversion of a…
CVE-2021-38187 — Critical (CVSS 9.8): An issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a…
CVE-2019-19317 — Critical (CVSS 9.8): lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which…
CVE-2019-14842 — Critical (CVSS 9.8): Structured reply is a feature of the newstyle NBD protocol allowing the server to send a reply in chunks. A bounds…
CVE-2018-8786 — Critical (CVSS 9.8): FreeRDP prior to version 2.0.0-rc4 contains an Integer Truncation that leads to a Heap-Based Buffer Overflow in…

Browse all CWE-681 vulnerabilities →