Menu

Star on GitHub · 3.2k

CVE-2026-3663

3.3 · LOW

A vulnerability was found in xlnt-community xlnt up to 1.6.1.

Published Mar 7, 2026CWE-119EPSS 0.20%

Overview

CVE-2026-3663 is a low-severity vulnerability. It was published on March 7, 2026 and has a CVSS 3.1 base score of 3.3 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

A vulnerability was found in xlnt-community xlnt up to 1.6.1. This issue affects the function xlnt::detail::compound_document_istreambuf::xsgetn of the file source/detail/cryptography/compound_document.cpp of the component XLSX File Parser. Performing a manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit has been made public and could be used. The patch is named 147. It is recommended to apply a patch to fix this issue.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-3663?

CVE-2026-3663 is a low-severity vulnerability. It was published on March 7, 2026 and has a CVSS 3.1 base score of 3.3 (LOW).

How severe is CVE-2026-3663?

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-3663?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-3663?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-3663 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2026

View all