CVE-2026-21049
Local out-of-bounds write in libpadm.so enabling arbitrary code execution.
Is CVE-2026-21049 being exploited?
Not confirmed. CVE-2026-21049 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-21049?
CVE-2026-21049 is rated High with a CVSS score of 8.4. 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-2026-21049?
Yes. A fix has been recorded for CVE-2026-21049. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-21049 affect?
CVE-2026-21049 affects Devices using libpadm.so prior to SMR Jul-2026 Release 1, Samsung Android devices (SMR < Jul-2026). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-21049?
Install SMR Jul-2026 Release 1 or vendor update; restrict untrusted local access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attackers can trigger an out-of-bounds write in libpadm.so to achieve arbitrary code execution and possible privilege escalation.
Patch when possible