# CVE-2026-54715: GoAccess: Heap Out-of-Bounds Write in parse_browser()

> A heap out-of-bounds write in GoAccess allows attackers to corrupt memory or crash the application via crafted User-Agent strings in access logs.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-54715, GHSA-qcx5-vh2x-35fr, UBUNTU-CVE-2026-54715

## What is CVE-2026-54715?

CVE-2026-54715 is a high-severity memory corruption vulnerability in allinurl goaccess, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. In version 1.10.2, parse_browser assumes the matched browser token begins with Opera and moves a trailing version substring to match plus five, allowing a crafted User-Agent in a processed access log to write one to four attacker-influenced bytes beyond the heap allocation and corrupt or crash GoAccess. This issue is fixed in version 1.11.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-54715?


## How do I fix CVE-2026-54715?

Upgrade to a fixed version.

## Is CVE-2026-54715 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54715 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54715 and fix it if it is affected.

What it is: CVE-2026-54715 is a high-severity memory corruption vulnerability in allinurl goaccess, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54715 exists.

Affected product: allinurl goaccess. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54715/ (Markdown: https://insights.sbomify.com/CVE-2026-54715/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54715
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54715
- OSV: https://osv.dev/vulnerability/CVE-2026-54715

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54715/
Summaries are generated and may contain mistakes; the official description above is the record.