CVSS 4.0
6.8 mediumCVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NMedium (6.8) in samsung android. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-21018 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-21018?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-21018?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-21018 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Samsung Mobile Devices | SMR May-2026 Release in Android 14, 15, 16 |
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.