CVE-2025-23272
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 · uneditedNVIDIA nvJPEG library contains a vulnerability where an attacker can cause an out-of-bounds read by means of a specially crafted JPEG file. A successful exploit of this vulnerability might lead to information disclosure or denial of service.
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 confidenceThe NVIDIA nvJPEG library has an out-of-bounds read vulnerability in its JPEG decoding logic. An attacker can trigger this by providing a specially crafted JPEG file, causing the library to read memory outside allocated buffers. This can lead to information disclosure (exposing sensitive memory contents) or denial of service (crash).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/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 nvJPEG library presenceSearch for nvJPEG library files on the system (e.g., libnvjpeg.so on Linux, nvjpeg.dll on Windows, or nvjpeg Python/CUDA packages)Affected if nvJPEG library is installed on the system
-
Determine nvJPEG versionRun nvjpeg_query_capability or check library version metadata; compare against NVIDIA security advisories for CVE-2025-23272Affected if Installed version matches the vulnerable version range from NVIDIA advisory
-
Identify JPEG processing usageReview application code, services, or system configurations that utilize nvJPEG for decoding JPEG imagesAffected if Applications or services process JPEG files using the nvJPEG library
-
Assess JPEG input source trustDetermine whether JPEG files processed by nvJPEG originate from untrusted sources (user uploads, network endpoints, external devices, or untrusted file paths)Affected if nvJPEG processes JPEG files from untrusted or external sources
-
Review for crash or memory anomaly logsCheck system and application logs for crashes, segmentation faults, or abnormal memory access errors occurring during JPEG decoding operationsAffected if Crashes or memory access violations are logged during JPEG processing
A system is affected if it runs a vulnerable version of the nvJPEG library and processes JPEG files, particularly from untrusted sources, as the out-of-bounds read requires the library to decode a specially crafted JPEG file.
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 dataApply the NVIDIA security patch when available; until then, validate and sanitize all JPEG input from untrusted sources before processing with nvJPEG.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23272 — 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-23272 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