Threats / Samsung / CVE-2025-21043
CVE-2025-21043
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Samsung Mobile Devices vulnerability
Samsung mobile devices contain an out-of-bounds write vulnerability in libimagecodec.quram.so that allows remote attackers to execute arbitrary code.
Verdict
Today item — known-exploited.
Out-of-bounds write in image codec library enables remote code execution on Samsung mobile devices. Active exploitation observed in the wild. Affects image processing functionality accessible to untrusted content.
CISA KEV Yes · 2025-10-025EPSS 0.019 (verify live)6CVSS 8.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-02).
Probability (EPSS)
EPSS 0.019 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Samsung, Mobile Devices. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 20 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious image file designed to trigger out-of-bounds memory writes in the image codec library.
Business
Device users face risk of arbitrary code execution when processing untrusted image content.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the malicious image to a target device through messaging, web browsing, or media sharing.
Business
Samsung must manage incident response and user notification for actively exploited vulnerability.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve code execution with the privileges of the image processing service.
Business
Customer trust and device security posture are compromised; remediation requires timely patching.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by SamsungMobileCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.