dbcve.org
VulnerabilityAwaiting classification

CVE-2026-21048

HIGH · 8.3 CVSS v4.0 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
Out-of-bounds write in parsing DNG format in libimagecodec.media.quram.so prior to SMR Jul-2026 Release 1 allows remote attackers to write 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 confidence

An out-of-bounds write vulnerability exists in the DNG (Digital Negative) image format parser within libimagecodec.media.quram.so on Samsung mobile devices running software prior to the July 2026 SMR release. The vulnerability allows remote attackers to write to memory locations outside allocated buffers by crafting malicious DNG image files, potentially leading to arbitrary code execution.

MitigationUpdate Samsung mobile devices to SMR July-2026 Release 1 or later to obtain the patched libimagecodec.media.quram.so library that properly validates bounds during DNG format parsing.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/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:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Samsung mobile device in use
    Identify the device model and manufacturer through Settings > About Phone or system information utilities
    Affected if The device is not a Samsung mobile device - this vulnerability only affects Samsung mobile devices
  2. Check current SMR (Samsung Maintenance Release) version
    Navigate to Settings > About Phone > Software Information > Build Number, or use 'getprop ro.build.version.sem' via ADB shell to retrieve the SMR version
    Affected if The SMR version is earlier than July-2026 (e.g., SMR June-2026, May-2026, or earlier) - only devices on versions prior to the July-2026 release are affected
  3. Verify libimagecodec.media.quram.so is present
    Use a file manager with root access or ADB shell to locate /system/lib/libimagecodec.media.quram.so (path may vary by Android version)
    Affected if The library file exists on the device - this confirms the vulnerable component is installed
  4. Confirm DNG image processing capability
    Check if the device camera can capture in DNG format (Camera settings > Save options > DNG) or if apps that process DNG images are installed
    Affected if The device has DNG capture enabled or processes DNG images - this is the attack surface for the vulnerability

If the device is a Samsung mobile device running an SMR version earlier than July-2026 with the libimagecodec.media.quram.so library present and DNG image processing enabled, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Samsung mobile devices to SMR July-2026 Release 1 or later to obtain the patched libimagecodec.media.quram.so library that properly validates bounds during DNG format parsing.

Recommended fix Moderate confidence

SMR Jul-2026 Release 1 (or later security maintenance release)

  1. Check your Samsung device model and current SMR (Samsung Maintenance Release) version in Settings > About Phone > Software Information
  2. Navigate to Settings > Software Update and download/install the latest security update
  3. Verify the installed SMR version is July-2026 Release 1 or later
  4. Alternatively, manually check for updates via Samsung Members app or your carrier's update service
Caveat Users should ensure they back up important data before applying system updates, as with any software upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21048 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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