openjpeg: Use of Uninitialized Variable
CVE-2025-54874 is a critical-severity use of uninitialized variable vulnerability in openjpeg from Uclouvain, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected openjpeg versions: >= 2.5.1, <= 2.5.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.66% chance of exploitation within 30 days, higher than 52% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of openjpeg you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.6 | Medium | CNA (github.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
OpenJPEG 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Uninitialized Variable
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
How developers prevent this class of flaw
- Ensure that critical variables are initialized before first use.
- Most compilers will complain about the use of uninitialized variables if warnings are turned on.
- When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
More Use of Uninitialized Variable vulnerabilities (CWE-457)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Technical write-ups (may include proof of concept)
- securitylab.github.com/advisories/GHSL-2025-057_OpenCVExploit, Third Party Advisory
Recent Use of Uninitialized Variable vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
- 8.6 High severity
- 8.8 High severity
- 7.7 High severity
Spotted an error? Tell us.