CVE-2025-58478
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 write 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 write vulnerability exists in libimagecodec.quram.so, a Samsung-specific image codec library, prior to the SMR Dec-2025 Release 1. This memory corruption flaw allows remote attackers to access out-of-bounds memory, potentially leading to arbitrary code execution or data disclosure.
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.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 13.0, 14.0, 15.0, or 16.0
-
Verify library presenceCheck for /vendor/lib64/libimagecodec.quram.so or /system/lib64/libimagecodec.quram.so using 'find / -name libimagecodec.quram.so 2>/dev/null' via ADB or a file managerAffected if The vulnerable library file exists on the device
-
Check Samsung security patch levelGo to Settings > About Phone > Software information > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than December 2025 or the SMR Dec-2025 Release 1 update has not been applied
-
Identify image processing usageReview which apps or processes access the libimagecodec.quram.so library by monitoring file access or reviewing app permissions for camera, gallery, or messaging appsAffected if Untrusted image files are processed by apps that load this library
The device is affected if it runs Android 13.0, 14.0, 15.0, or 16.0, contains the libimagecodec.quram.so library, and has not received the Samsung SMR Dec-2025 Release 1 security 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 Samsung SMR Dec-2025 Release 1 firmware update to affected devices. Until patched, restrict processing of untrusted image files and monitor for indicators of compromise.
SMR Dec-2025 Release 1 (December 2025 Security Patch Level)
- Navigate to Settings > About phone on the Samsung device
- Check the Android security patch level - ensure it shows 'December 2025' or SMR Dec-2025 Release 1
- If a newer security update is available, go to Settings > Software update and tap 'Download and install'
- Restart the device after the update completes
- Verify the security patch level has been updated to December 2025 in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58478 — 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-58478 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