dbcve.org
VulnerabilityAwaiting classification

CVE-2026-21049

HIGH · 8.4 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 →
86/100
Remediation priority · High
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 libpadm.so library prior to SMR Jul-2026 Release 1 allows local attackers to execute arbitrary code.

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 the libpadm.so library on Samsung devices running firmware versions prior to the July 2026 SMR release. The out-of-bounds write condition allows a local attacker to achieve arbitrary code execution, potentially granting privileged access to the device.

MitigationApply the SMR Jul-2026 Release 1 or later firmware update to affected Samsung devices to patch the vulnerable libpadm.so library.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/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. Confirm device is a Samsung product
    Check system properties: run 'getprop ro.product.brand' or 'getprop ro.manufacturer' and verify the output shows Samsung
    Affected if Device is not a Samsung product (this CVE affects only Samsung devices)
  2. Check the Android security patch level
    Run 'getprop ro.build.version.security_patch' to retrieve the installed security patch date
    Affected if The security patch date is earlier than July 2026 (format typically shows as YYYY-MM-DD)
  3. Check the Samsung SMR (Security Maintenance Release) version
    Run 'getprop ro.build.version.sem_platform' or check Settings > About Phone > Software Information > Security patch level
    Affected if The SMR version is below the July-2026 release (compare to the Jul-2026 SMR baseline)
  4. Verify libpadm.so library is present on the device
    Check if the library exists by running 'ls -la /vendor/lib64/libpadm.so' or 'find / -name libpadm.so 2>/dev/null'
    Affected if The library file libpadm.so is present on the device (vulnerability resides in this library)
  5. Confirm firmware build date is prior to July 2026
    Run 'getprop ro.build.date' or check the build number in Settings > About Phone > Software Information > Build number
    Affected if Build date is before July 2026 (this indicates firmware predates the fix)

A Samsung device is affected if it has libpadm.so present AND its security patch level or SMR version is earlier than the July 2026 release.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SMR Jul-2026 Release 1 or later firmware update to affected Samsung devices to patch the vulnerable libpadm.so library.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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