vulnerability

CVE-2025-21043

8.8

High

KEV · Exploited in wildEPSS 2%Patch available

Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to execute arbitrary code.

exploited

Yes, in CISA KEV since 2 Oct 2025fix by 23 Oct 2025 (CISA deadline for US federal agencies)

fix

Patch available see the advisory in the references

likelihood

EPSS 2.2%

Published 12 Sept 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage

server-sideruntimeWAF can block: noAV · networkCWE-787· Out-of-Bounds Write

Can a WAF block it? No. This is an out-of-bounds write, a memory-corruption bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector

attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegrityhighavailabilityhigh

CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

common questions

Is CVE-2025-21043 being exploited?

Yes. CVE-2025-21043 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-21043?

CVE-2025-21043 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-21043?

Yes. A fix has been recorded for CVE-2025-21043. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-21043 affect?

CVE-2025-21043 affects samsung:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

samsung:android

cisa ssvc

exploitation: active
automatable: no
technical impact: total

Assessed by CISA 2 Oct 2025 (SSVC 2.0.3).

timeline

12 Sept 2025Published
2 Oct 2025Added to CISA KEV (exploited in the wild) · 20 days later
2 Oct 2025CISA SSVC assessment: exploitation active · same day later
23 Oct 2025CISA remediation due date (US federal agencies) · 21 days later
7 Oct 2026CVE record last updated · 350 days (about 12 months) later
2 Nov 2026Analysed by vulneraibility.com · 26 days later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 links

Linksecurity.samsungmobile.com /securityUpdate.smsb?year=2025&month=09
Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-21043

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free