dbcve.org
OpencvApplication

CVE-2025-53644

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-17
Fix available
A fix is available. Upgrade to 4.12.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
OpenCV is an Open Source Computer Vision Library. Versions 4.10.0 and 4.11.0 have an uninitialized pointer variable on stack that may lead to arbitrary heap buffer write when reading crafted JPEG images. Version 4.12.0 fixes the vulnerability.

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

OpenCV versions 4.10.0 and 4.11.0 contain an uninitialized pointer variable allocated on the stack during JPEG image parsing. When processing a specially crafted JPEG file, this uninitialized pointer can be dereferenced, leading to arbitrary heap buffer writes and potential remote code execution.

MitigationUpgrade to OpenCV 4.12.0 or later. If immediate patching is not feasible, restrict OpenCV's access to untrusted JPEG input sources and consider network segmentation as a compensating control.

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
OpencvApplication
Affected:>= 4.10.0, < 4.12.0

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 installed OpenCV version
    Run 'pkg-config --modversion opencv4' or 'opencv_version' command, or inspect the shared library file (e.g., libopencv_core.so) properties to determine the compiled version number
    Affected if Version is 4.10.0 or 4.11.0 (versions 4.12.0 and later are not affected)
  2. Confirm JPEG decoding support is present
    Check if OpenCV was built with JPEG support by examining loaded modules: run 'opencv_version --verbose' or inspect linked libraries for 'libopencv_imgcodecs.so' and 'libjpeg' presence
    Affected if JPEG image codecs are compiled into OpenCV and available for use
  3. Identify JPEG processing code paths
    Review application source code or runtime behavior to locate calls to imread(), imdecode(), or VideoCapture reading JPEG frames, especially from file, network, or user-supplied input sources
    Affected if Application decodes or processes JPEG images from any untrusted input source

The environment is affected if OpenCV version is 4.10.0 or 4.11.0 and the application uses any JPEG decoding functionality.

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 4.12.0 or later
Fixed in 4.12.0
Vendor patch github.com →
Interim mitigation

Upgrade to OpenCV 4.12.0 or later. If immediate patching is not feasible, restrict OpenCV's access to untrusted JPEG input sources and consider network segmentation as a compensating control.

Recommended fix High confidence

4.12.0

  1. Identify all deployments/systems running OpenCV versions 4.10.0 or 4.11.0
  2. Plan maintenance window for upgrade (as library upgrade may require rebuilding dependent applications)
  3. Download or obtain OpenCV version 4.12.0 from the official source (https://opencv.org/releases/)
  4. Rebuild and recompile any applications or services that link against the OpenCV library
  5. Replace the vulnerable OpenCV library binaries with the version 4.12.0 binaries
  6. Rebuild any dependent applications to link against the new library version
  7. Test the environment to ensure applications function correctly with the updated library
  8. Deploy the updated components to production
Caveat Minor: Verify compatibility of any custom code using OpenCV APIs, as point releases typically maintain API compatibility but may have behavioral changes

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

Fix this in Opencv Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53644 — 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-53644 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