dbcve.org
VulnerabilityAwaiting classification

CVE-2026-21045

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 TIFF 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

A memory corruption vulnerability exists in libimagecodec.media.quram.so when parsing TIFF format images. The library improperly handles boundary checks during image decoding, allowing an attacker to trigger an out-of-bounds write operation by supplying a specially crafted malicious TIFF file. This could lead to arbitrary memory corruption, potentially enabling remote code execution or denial of service.

MitigationUpdate the libimagecodec.media.quram.so library to the SMR Jul-2026 Release 1 or later which contains the patched version. Treat all incoming TIFF files from untrusted sources as potentially malicious until the patch is applied.

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. Locate the vulnerable library file
    Search for libimagecodec.media.quram.so in system directories. Common paths include /system/lib/, /vendor/lib/, or /system/vendor/lib/. Use: find / -name 'libimagecodec.media.quram.so' 2>/dev/null
    Affected if The library file exists on the system - this indicates the component is present and potentially vulnerable
  2. Determine library version or build date
    Use the 'ls -la' command on the found library file to check its modification timestamp, or use 'getprop ro.libimagecodec.media.quram.so.version' if available. Check any version metadata using: strings <path_to_library> | grep -i version
    Affected if The library version or date is earlier than the SMR Jul-2026 Release 1 patch, or no version information is available to confirm otherwise
  3. Verify TIFF image processing is enabled
    Check if the device or application has TIFF decoding enabled. On Android, examine /system/etc/media_codecs.xml or /system/etc/media_codecs_performance.xml for image codec entries. Look for 'image/tiff' or 'tiff' in the codec configuration
    Affected if TIFF decoding support is present in the media codec configuration, meaning the vulnerable code path can be triggered
  4. Confirm exposure to untrusted TIFF sources
    Review application logs or network traffic for TIFF file processing from external or untrusted sources. Check if messaging apps, browsers, or file managers can receive or open TIFF attachments. Query: grep -r 'tiff\|TIFF' /data/log/ 2>/dev/null | head -20
    Affected if The system or any installed application processes TIFF files from untrusted or external sources without sanitization

The system is affected if libimagecodec.media.quram.so is present with a version predating the SMR Jul-2026 Release 1 patch AND the device or applications process TIFF images from potentially untrusted sources.

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 the libimagecodec.media.quram.so library to the SMR Jul-2026 Release 1 or later which contains the patched version. Treat all incoming TIFF files from untrusted sources as potentially malicious until the patch is applied.

Recommended fix Moderate confidence

SMR Jul-2026 Release 1

  1. Check your Samsung device for system updates
  2. Locate and install the SMR (Samsung Monthly Release) July-2026 update or later
  3. Verify the update was successfully applied after installation

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21045 — 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-21045 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