# CVE-2026-129135: picoquic before 2026.11.05.3e2e3d3 Integer Overflow via TIME_STAMP Frame Decoder


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-3x7x-3p6v-f98v

## What is CVE-2026-129135?

CVE-2026-129135 is a medium-severity vulnerability in private-octopus picoquic, published on 13 Nov 2026. 

### Official description

picoquic before 2026.11.05.3e2e3d3 contains an integer overflow vulnerability in picoquic_decode_time_stamp_frame() that allows remote QUIC peers to corrupt stored timestamps by sending oversized TIME_STAMP values. Attackers on connections negotiating the TIME_STAMP extension can send large values shifted by ack_delay_exponent to wrap the result, corrupting RTT and bandwidth estimation and degrading congestion control.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

1 open source package ship an affected version, including private-octopus/picoquic.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `private-octopus/picoquic` | GitHub | `pkg:github/private-octopus/picoquic` | All versions | 2026.11.05.3e2e3d3 |

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

Upgrade private-octopus/picoquic to 2026.11.05.3e2e3d3 or later.

## Is CVE-2026-129135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129135 is a medium-severity vulnerability in private-octopus picoquic, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129135 in the wild and no public exploit code.

Affected packages and fixed versions:
- private-octopus/picoquic (GitHub): affected all versions; fixed in 2026.11.05.3e2e3d3

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-129135/ (Markdown: https://insights.sbomify.com/CVE-2026-129135/index.md)
```

## Sources

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

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