CVE-2025-58479
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 · uneditedOut-of-bounds read in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds memory.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in libimagecodec.quram.so, a Samsung image codec library, prior to the SMR Dec-2025 Release 1. The flaw allows remote attackers to access memory outside allocated buffers, potentially leading to information disclosure or denial of service.
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= 13.0= 14.0= 15.0= 16.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installed Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version is 13.0, 14.0, 15.0, or 16.0
-
Locate the image codec librarySearch for libimagecodec.quram.so on the device filesystem, typically found in /vendor/lib/ or /system/lib/Affected if The library file exists on the device (indicating the vulnerable component is present)
-
Check firmware/SMR versionRun 'getprop ro.build.version.sem' or check Settings > About Phone > Software version to identify the SMR (Samsung Maintenance Release) dateAffected if The SMR version is earlier than December 2025 Release 1, or the SMR cannot be determined/is missing
-
Inspect library version if availableUse 'ls -la' on the libimagecodec.quram.so file to check its modification date, or use a tool like 'strings' to look for version indicators within the library binaryAffected if The library version corresponds to a build predating the Dec-2025 patch release
A user is affected if they are running Android 13.0-16.0 on a Samsung device with the vulnerable libimagecodec.quram.so library present and the device has not received the SMR Dec-2025 Release 1 update.
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.
dbcve · scopedApply the SMR Dec-2025 Release 1 or later patch which contains the fixed libimagecodec.quram.so library; users should update their Samsung firmware accordingly.
SMR Dec-2025 Release 1 (December 2025 Samsung Security Maintenance Release)
- 1. Navigate to Settings > Security and privacy > Security update on the Samsung device
- 2. Check for and install the latest Samsung Security Maintenance Release (SMR)
- 3. Ensure the installed SMR is December 2025 Release 1 or later (SMR Dec-2025 Release 1)
- 4. Verify the patch has been applied by checking the security patch date in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58479 — 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-58479 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