Quick answers
- Is CVE-2026-55777 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55777 being exploited in the wild.
- How severe is CVE-2026-55777?
- Informational severity, with a CVSS score of 5.3, published 30 July 2026.
- Which products and versions are affected?
- Allinurl GoAccess < 1.11.
- Is there a fix for CVE-2026-55777?
- A patch was published on 2026-07-30: Fixed in version 1.11 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55777 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-55777?
- Check whether you run Allinurl GoAccess at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based out-of-bounds read exists in GoAccess prior to version 1.11 within the `parse_ios()` function in `src/opesys.c`. The vulnerability is caused by the incorrect use of an attacker-controlled offset as both the source offset and the copy length in a `memmove()` call. By providing a User-Agent string with excessive padding between an iOS keyword (e.g., iPhone) and the " OS " token, an attacker can cause the function to read up to 4 KB beyond the allocated heap buffer. While primarily resulting in a denial of service (SIGSEGV) when hitting unmapped memory or guard pages, it represents a significant spatial memory safety violation. The issue is reachable remotely if GoAccess is configured to analyze logs containing attacker-supplied User-Agent headers. This was fixed in version 1.11 by tightening the iOS version suffix parsing logic.
Affected products
- allinurl GoAccess < 1.11
Timeline
- 2026-07-20: advisory: GitHub Security Advisory published
- 2026-07-30: disclosed: CVE published to NVD
- 2026-07-30: patched: Fixed in version 1.11