CVE
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.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.11
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. fqterm before 0.9.11 A malicious server sends CSI sequences with 30 or more semicolon-separated parameters
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.
Original 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.
Who should check
Anyone running fqterm before 0.9.11 to connect to telnet, SSH or BBS hosts
“Affecting fqterm >= 0, < 0.9.11”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
fqterm before 0.9.11 A malicious server sends CSI sequences with 30 or more semicolon-separated parametersUpgrade to a fixed version: 0.9.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Iru Cai fqterm
fixed in 0.9.11
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131875 |
| Record | NVD · CVE-2026-131875 |
| Other links 4 | |
| Patch | GitHub · mytbk/fqterm · Commit e340b62d |
| Repository | GitHub · mytbk/fqterm · Release 0.9.11 |
| Repository | GitHub · mytbk/fqterm · Repository |
| Link | vulncheck.com · advisories/fqterm-before-0.9.11-heap-out-of-bounds-write-via-fqtermdecode-csi-parameters |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131875
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-131875?
fqterm: before 0.9.11.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com