# CVE-2026-131876: fqterm 0.9.9 before 0.9.11 SSH Client Out-of-Bounds Memory Access via Server Lengths


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-131876, GHSA-mq5p-mpj4-pp27, UBUNTU-CVE-2026-131876

## What is CVE-2026-131876?

CVE-2026-131876 is a high-severity vulnerability in Iru Cai fqterm, published on 18 Nov 2026. 

### Official description

fqterm 0.9.9 before 0.9.11 contains an out-of-bounds memory access vulnerability in its SSH client that trusts unchecked server-supplied length fields for allocations, copies and read positions. Malicious servers or man-in-the-middle attackers can send crafted lengths in getString(), KEXINIT name-lists, key parsing or packet framing before host key verification to crash the client.

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

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

1 open source package ship an affected version, including mytbk/fqterm.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `mytbk/fqterm` | GitHub | `pkg:github/mytbk/fqterm` | From 0.9.9 | 0.9.11 |

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

Upgrade mytbk/fqterm to 0.9.11 or later.

## Is CVE-2026-131876 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131876 is a high-severity vulnerability in Iru Cai fqterm, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131876 in the wild and no public exploit code.

Affected packages and fixed versions:
- mytbk/fqterm (GitHub): affected from 0.9.9; fixed in 0.9.11

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

## Sources

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

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