CVE-2025-47436: Apache Orc buffer overflow (CVSS 9.8)

Description

Heap-based Buffer Overflow vulnerability in Apache ORC. A vulnerability has been identified in the ORC C++ LZO decompression logic, where specially crafted malformed ORC files can cause the decompressor to allocate a 250-byte buffer but then attempts to copy 295 bytes into it. It causes memory corruption. This issue affects Apache ORC C++ library: through 1.8.8, from 1.9.0 through 1.9.5, from 2.0.0 through 2.0.4, from 2.1.0 through 2.1.1. Users are recommended to upgrade to version 1.8.9, 1.9.6, 2.0.5, and 2.1.2, which fix the issue.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Apache Orc≥ 1.9.0 < 1.9.6 · ≥ 2.0.0 < 2.0.5 · ≥ 2.1.0 < 2.1.2 · < 1.8.9

Remediation

Fixed in

Apache Orc≥ 1.9.6

Patch & vendor advisories

https://lists.apache.org/thread/kd6tlv8fs5jybmsgxr4vrkdxyc866wrn

References

https://lists.apache.org/thread/kd6tlv8fs5jybmsgxr4vrkdxyc866wrnMailing ListVendor Advisory
https://orc.apache.org/security/CVE-2025-47436/Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/05/13/4Mailing ListThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-47436 being actively exploited?

CVE-2025-47436 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.53%.

How severe is CVE-2025-47436?

CVE-2025-47436 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.53% probability of exploitation.

Which products are affected by CVE-2025-47436?

Affected products include Apache Orc.

How do I fix CVE-2025-47436?

Upgrade affected software to a fixed version, for example Apache Orc 1.9.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-47436 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo