Skip to main content

catdoc CVE-2026-111127

| EUVDEUVD-2026-102358 MEDIUM
Out-of-bounds Read (CWE-125)
2026-10-15 VulnCheck GHSA-f7rh-84jf-2xrr
6.9
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted .xls to victim
  2. Exploit
    Victim runs xls2csv on file
  3. Execution
    Oversized unicode count triggers OOB read
  4. Impact
    Adjacent memory leaked to CSV or crash

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that a victim user or an automated pipeline process an attacker-supplied, specially crafted .xls file through catdoc's xls2csv tool; the file must declare 0xFFFF two-byte characters in a LABEL, STRING, or SST record so that copy_unicode_string() reads beyond the buffer. Limiting factors: the attack is local (AV:L) and gated by user interaction (UI:P) - the victim must actively invoke xls2csv on the malicious file - and only catdoc versions through 0.95 are affected. No non-default configuration is required beyond using the xls2csv functionality. Risk rises materially in server-side contexts that auto-process untrusted documents, where the required 'interaction' is performed by the service rather than a human.

Impact

This is a genuine but moderate-severity issue, best characterized as a high-impact-in-narrow-contexts flaw rather than a mass-exploitation priority. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H) scores 6.9 (Medium): the attack is local and requires passive user interaction (a victim must run xls2csv on an attacker-supplied .xls file), which sharply limits remote, automated exploitation. Impact is split - low confidentiality (VC:L, adjacent heap/stack bytes leaked into CSV output) and high availability (VA:H, process crash) - with no integrity impact and no code execution, consistent with CWE-125 (out-of-bounds read, not a write). No CISA KEV listing and no explicit POC/exploit-code flag were provided in the input, so exploitation is theoretical at analysis time, though a detailed public technical write-up (hackmd) and the exact vulnerable source lines are referenced, lowering the bar for a working PoC. There are no strongly conflicting signals: the Medium CVSS, absence of KEV, and local/UI-gated vector all point to limited real-world urgency. One caveat for defenders: the 'local' vector understates risk in server-side document-processing pipelines (indexers, antivirus pre-processors, mail gateways) that invoke catdoc automatically on untrusted files - in those deployments a 'crafted file' effectively becomes remotely deliverable even though CVSS rates it AV:L.

Exploit ScenarioDerived

An attacker crafts a malicious .xls file whose LABEL, STRING, or SST record declares 0xFFFF two-byte characters, then delivers it (e.g., via email attachment or upload) to a victim or a document-processing system. When the file is converted using xls2csv, copy_unicode_string() reads past the allocated buffer, leaking adjacent memory contents into the CSV output or crashing the process. No public exploit code was identified in the provided data, though a detailed technical write-up and the exact vulnerable source lines are publicly referenced.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 15, 2026

An out-of-bounds read in catdoc's xls2csv converter lets an attacker who supplies a crafted .xls file cause the tool to read past the end of a heap buffer and emit adjacent memory contents into the converted CSV output, or crash the process outright. The flaw lives in copy_unicode_string() in src/xlsparse.c and is triggered when a LABEL, STRING, or SST record declares 0xFFFF two-byte characters, a count that is consumed without adequate validation against the actual buffer size. All catdoc versions through 0.95 are affected, and exploitation requires a victim or an automated document-processing pipeline to open the malicious spreadsheet with xls2csv; the impact is therefore moderate in human-driven workflows but materially higher where untrusted spreadsheets are converted automatically, and no public exploit code was identified at time of analysis.

RemediationAI

No vendor-released patch was identified at time of analysis, and the vulnerable behavior is present in the upstream source through version 0.95, so teams cannot rely on a simple version bump and must either patch the code themselves or remove the parsing path from untrusted input. The most direct fix is to modify copy_unicode_string() in src/xlsparse.c so the declared character count is validated against the remaining bytes in the record buffer before any copy occurs, rejecting records whose length exceeds the available data; because the upstream project is lightly maintained, downstream distributions and vendors that bundle catdoc should be tracked for a backported fix. Where patching is not feasible, the highest-value compensating control is to stop feeding untrusted .xls files to xls2csv: replace it in document-conversion pipelines with a maintained parser such as LibreOffice in headless mode, Python's openpyxl/xlrd, or Apache POI, accepting the trade-off of a larger dependency footprint and different output formatting. If catdoc must continue processing untrusted spreadsheets, isolate xls2csv in a sandboxed, low-privilege container with no network access and a read-only filesystem, and restrict or discard its stdout so that any leaked adjacent heap memory is not written to a shared location; note that this does not eliminate the denial-of-service aspect, since a malformed record can still crash the process, so callers should wrap invocations with timeouts and treat non-zero exits as expected. Additional hardening includes compiling catdoc with modern stack and heap protections, running it under a strict memory limit, and funneling all untrusted documents through a content-validation gateway that rejects implausible BIFF string-length fields before conversion; each of these reduces but does not remove the information-disclosure risk, so patching or replacing the parser remains the durable remedy.

Affected VersionsENISA

catdoc 0 ≤0.95

Affected Packages

euvd catdoc no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

catdoc is a legacy C utility that extracts text from Microsoft Office binary formats, and its Excel handling is implemented in src/xlsparse.c, which walks the BIFF (Binary Interchange File Format) record stream of .xls workbooks. The vulnerable routine, copy_unicode_string() (roughly lines 421-520 in the upstream source), converts BIFF string payloads into catdoc's internal text representation; it trusts the character-count field carried in LABEL, STRING, and SST (Shared String Table) records when sizing its read from the record buffer. By declaring 0xFFFF two-byte characters, an attacker causes the routine to walk far past the end of the allocated record buffer, which classifies as CWE-125 (Out-of-Bounds Read). The primary data-exposure path is not a direct memory read by the attacker but an information-disclosure side channel: the over-read bytes are copied into the text stream that xls2csv writes to stdout or a file, potentially leaking heap contents from the parsing process. The same over-read can also walk into unmapped memory and abort the process, giving a denial-of-service effect that the assessing CVSS vector captures as a high availability impact (A:H). Because the code parses fully attacker-controlled input with raw pointer arithmetic and no bounds validation, the root cause is a classic unchecked-length-versus-buffer-size mismatch rather than an exploitation primitive like memory corruption or code execution.

Know when Catdoc gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.1 MEDIUM

Exploited by processing a local attacker-supplied file (AV:L) requiring the victim to run xls2csv (UI:R); yields limited memory disclosure (C:L) and reliable crash (A:H), no integrity impact.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

catdoc through 0.95 contains an out-of-bounds read vulnerability in copy_unicode_string() in src/xlsparse.c that allows attackers to read past buffers via an unchecked string character count. Attackers can supply a crafted .xls file declaring 0xFFFF two-byte characters in LABEL, STRING, or SST records to disclose adjacent memory through xls2csv output or crash the process.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche CLI document-conversion utility; packaged in Linux distros but small production footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy