# CVE-2026-130849: BZFlag bzfs before 2.4.32 Heap Out-of-Bounds Write via NetHandler::tcpReceive()


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-9q5f-g948-c95m, UBUNTU-CVE-2026-130849

## What is CVE-2026-130849?

CVE-2026-130849 is a critical vulnerability in BZFlag-Dev bzflag, published on 17 Nov 2026. 

### Official description

BZFlag bzfs before 2.4.32 contains a heap out-of-bounds write vulnerability in NetHandler::tcpReceive() that allows remote unauthenticated attackers to corrupt heap memory by sending a TCP message with a body length of exactly 1024. Attackers can overwrite the tcplen receive offset with a negative value to write controlled bytes before the buffer, crashing the server or executing commands as the bzfs user.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Upgrade BZFlag-Dev bzflag to 2.4.32 or later. The advisory says that version fixes it.

## Is CVE-2026-130849 being exploited?

There is no known exploitation of CVE-2026-130849 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130849 is a critical vulnerability in BZFlag-Dev bzflag, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130849 in the wild and no public exploit code.

Affected product: BZFlag-Dev bzflag. 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-130849/ (Markdown: https://insights.sbomify.com/CVE-2026-130849/index.md)
```

## Sources

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

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