dbcve.org
OrcApplication · Apache

CVE-2025-47436

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 1.8.9 / 1.9.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in Apache ORC C++ library's LZO decompression logic where malformed ORC files cause the decompressor to allocate a 250-byte buffer but attempt to copy 295 bytes into it, resulting in heap memory corruption.

MitigationUpgrade to version 1.8.9, 1.9.6, 2.0.5, or 2.1.2. Until upgraded, avoid processing untrusted ORC files as they can trigger the overflow.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OrcApplication
Affected:< 1.8.9>= 1.9.0, < 1.9.6>= 2.0.0, < 2.0.5>= 2.1.0, < 2.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Apache ORC library version
    Check the version of the Apache ORC C++ library or package installed in your environment. This may be found via package manager (e.g., rpm, dpkg, pip show orc), build metadata, or the library binary itself.
    Affected if The installed version falls within any of these ranges: < 1.8.9, >= 1.9.0 and < 1.9.6, >= 2.0.0 and < 2.0.5, or >= 2.1.0 and < 2.1.2
  2. Determine if LZO compression is used for ORC files
    Inspect your ORC files or processing pipeline to identify whether LZO compression is enabled. Check the compression codec configured for ORC file creation or reading (commonly visible in file metadata, schema, or compression settings).
    Affected if LZO compression is enabled for ORC files being processed by the vulnerable library version
  3. Locate ORC files in the environment
    Search directories where ORC files are stored or processed to identify any files that may have been created with LZO compression. Use file inspection tools or query your data pipeline configuration.
    Affected if LZO-compressed ORC files exist in environments running the vulnerable Apache ORC version
  4. Review processing logs for LZO-related errors
    Examine application or processing logs for any errors related to LZO decompression of ORC files. While not a definitive indicator of this specific flaw, repeated LZO decompression issues may warrant investigation.
    Affected if The environment processes LZO-compressed ORC files using a version known to be affected

You are affected if the Apache ORC library version is vulnerable (within the ranges listed) AND your environment processes ORC files using LZO compression.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.9 / 1.9.6 / 2.0.5 or later
Fixed in 1.8.91.9.62.0.5
Interim mitigation

Upgrade to version 1.8.9, 1.9.6, 2.0.5, or 2.1.2. Until upgraded, avoid processing untrusted ORC files as they can trigger the overflow.

Recommended fix High confidence

1.8.9, 1.9.6, 2.0.5, or 2.1.2 (depending on current major.minor series)

  1. Identify the current Apache ORC version in use by checking project dependencies or library version
  2. Determine which upgrade path applies based on your current major.minor version: 1.8.x -> 1.8.9, 1.9.x -> 1.9.6, 2.0.x -> 2.0.5, or 2.1.x -> 2.1.2
  3. Download the appropriate fixed release from the official Apache ORC repository (https://orc.apache.org/downloads/) or update package manager dependencies
  4. Replace the vulnerable ORC C++ library with the fixed version
  5. Rebuild any projects that link against the ORC library
  6. Verify the new version is correctly installed (e.g., orc-version should report the fixed release)
  7. Re-test ORC file processing functionality to confirm the fix works
Caveat Minimal risk when upgrading within same major.minor series; cross-series upgrades (e.g., 1.8.x to 2.x) may require compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Orc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47436 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data