# CVE-2026-119600: tcpflow < 1.7.0 Out-of-Bounds Read via TCP Demultiplexer Payload Length


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-119600, GHSA-rjcg-fcj6-3hq4, UBUNTU-CVE-2026-119600

## What is CVE-2026-119600?

CVE-2026-119600 is a medium-severity vulnerability in simsong tcpflow, published on 30 Oct 2026. 

### Official description

tcpflow before 1.7.0 contains an out-of-bounds read vulnerability that allows unauthenticated attackers to read process memory by sending packets with forged IP payload lengths. Attackers can inject crafted IPv4 or IPv6 TCP packets into captured traffic or pcap files to leak adjacent memory into reconstructed flow files or crash tcpflow.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

No fix has been published for CVE-2026-119600 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119600 is a medium-severity vulnerability in simsong tcpflow, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119600 in the wild and no public exploit code.

Affected product: simsong tcpflow. 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-119600/ (Markdown: https://insights.sbomify.com/CVE-2026-119600/index.md)
```

## Sources

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

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