CVE-2025-53644
Opencv 4.10.0 – 4.12.0
Raw vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-53644 is a medium-severity Use of Uninitialized Variable (CWE-457) vulnerability in Opencv Opencv. Its CVSS base score is 6.6 (Medium).
Operationally, ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as Computer Vision; in the Supply Chain and Deployment risk domain.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-53644 affects OpenCV, an open-source computer vision library, specifically versions 4.10.0 and 4.11.0. The vulnerability stems from an uninitialized pointer variable on the stack, which can lead to an arbitrary heap buffer write when processing crafted JPEG images. This issue is classified under CWE-457 (Use of Uninitialized Variable) and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity due to its potential for high-impact confidentiality, integrity, and availability consequences.
Attackers can exploit this vulnerability remotely over the network with low complexity, requiring no privileges or user interaction. Any unauthenticated remote actor could supply a maliciously crafted JPEG image to an application using the affected OpenCV versions for image decoding, triggering the uninitialized pointer dereference and enabling arbitrary heap buffer writes. Successful exploitation could allow attackers to overwrite heap memory, potentially leading to remote code execution, data corruption, or denial of service, depending on the application's context and privileges.
Mitigation is available through upgrading to OpenCV version 4.12.0, which addresses the issue via a specific commit (a39db41390de546d18962ee1278bd6dbb715f466). Official advisories, including GitHub Security Lab's GHSL-2025-057 and the related issue tracker (#27271), confirm the fix in the 4.12.0 release and recommend immediate patching for affected deployments.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21795
Vulnerability Data
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.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Computer Vision
- Risk Domain
- Supply Chain and Deployment
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: opencv
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Secure development life cycle mandates practices that reduce uninitialized-variable defects.
Application security requirements can specify initialization rules, but the control itself does not directly address the weakness.
Secure coding explicitly requires variable initialization and static-analysis checks.
Secure architecture principles encourage defensive coding that can mitigate uninitialized variables.