CVE-2025-54874
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 · uneditedOpenJPEG is an open-source JPEG 2000 codec. In OpenJPEG from 2.5.1 through 2.5.3, a call to opj_jp2_read_header may lead to OOB heap memory write when the data stream p_stream is too short and p_image is not initialized.
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 confidenceA heap-based out-of-bounds write vulnerability exists in OpenJPEG's opj_jp2_read_header function. When processing a JPEG 2000 data stream that is shorter than expected and the p_image parameter is not properly initialized, the function can write beyond allocated buffer boundaries, potentially allowing arbitrary code execution.
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<= 2.5.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenJPEG library versionRun 'openjpeg --version' or check library file version metadata (e.g., libopenjp2.so.*). On Linux: 'dpkg -l | grep openjpeg' or 'rpm -qa | grep openjpeg'. On Windows: right-click the DLL and view Properties > Details > File Version.Affected if Version is 2.5.3 or lower (any version <= 2.5.3)
-
Verify if application uses opj_jp2_read_headerSearch source code for calls to 'opj_jp2_read_header' function. Use 'grep -r "opj_jp2_read_header" /path/to/source' or inspect binary for this symbol using 'nm' or 'objdump'.Affected if Code invokes opj_jp2_read_header to parse JPEG 2000 streams
-
Confirm input handling of JP2 filesInspect how JPEG 2000 files are processed: check file input routines, ensure stream length validation occurs before calling opj_jp2_read_header, and verify that the p_image parameter is initialized to NULL before the call.Affected if Application processes JP2/J2K files from untrusted sources without validating stream length beforehand
-
Check for usage of older OpenJPEG bindingsIf using language bindings (Python openjpeg, Java bindings, etc.), verify the underlying library version. Check package manager for binding version and its dependency on libopenjp2.Affected if Bindings depend on OpenJPEG library version <= 2.5.3
You are affected if your OpenJPEG library version is 2.5.3 or lower and your application uses opj_jp2_read_header to process JPEG 2000 files from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to OpenJPEG version 2.5.4 or later when available; alternatively, ensure proper validation of input stream length and initialize all pointer parameters before calling opj_jp2_read_header.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54874 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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