CVE-2026-2703

What it is

A weakness has been identified in xlnt-community xlnt up to 1.6.1. Impacted is the function xlnt::detail::decode_base64 of the file source/detail/cryptography/base64.cpp of the component Encrypted XLSX File Parser. Executing a manipulation can lead to off-by-one. The attack requires local access. The exploit has been made available to the public and could be used for attacks. This patch is called f2d7bf494e5c52706843cf7eb9892821bffb0734. Applying a patch is advised to resolve this issue.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-02-19 07:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:31 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 1.9 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-02-19 07:17 UTC

Last modified

2026-06-17 10:31 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-189

Record status

Analyzed

Affected

• xlnt-community Xlnt ≤ 1.6.1

Attack profile CVSS 4.0 · 1.9

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

None

Integrity

None

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-2703.md and follow it. Check whether this project is affected by CVE-2026-2703. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge