CVE-2026-0119
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 · uneditedIn usim_SendMCCMNCIndMsg of usim_Registration.c, there is a possible out of bounds write due to memory corruption. This could lead to physical escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceAn out-of-bounds write vulnerability exists in the usim_SendMCCMNCIndMsg function within usim_Registration.c, causing memory corruption that enables physical escalation of privilege without requiring additional execution privileges or user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify baseband/modem firmware versionOn Android, go to Settings > About Phone > SIM Status or use 'AT+CGMR' command via terminal/ADB to query modem firmware version. Check your device manufacturer's documentation for the specific location of baseband version information.Affected if The displayed baseband firmware version cannot be verified against a patched release from your device or chipset vendor, or no patch information is available.
-
Confirm USIM functionality is activeVerify the device has cellular connectivity and a USIM card is inserted and recognized. Check that the device shows carrier signal and SIM status in Settings > About Phone > SIM Status or Settings > Connections > SIM card manager.Affected if USIM is active and the baseband firmware version is not confirmed as patched by the vendor.
-
Check vendor security bulletinReview your device manufacturer (OEM) and carrier security bulletins or patch notices for CVE-2026-0119. Look for USIM, registration code, or memory corruption fixes in the modem/baseband patch list.Affected if No vendor bulletin confirms a patch for this CVE and your baseband version predates the patch release date.
-
Verify physical access controlsAssess whether the device is in an environment where untrusted physical access is possible, as the vulnerability requires physical proximity to exploit.Affected if The device can be accessed physically by untrusted individuals and the baseband firmware is unpatched.
Your device is affected if it runs any Android version with an unpatched baseband/modem firmware containing the vulnerable USIM registration code, particularly when physical access to the device is possible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patches or firmware updates for the USIM component addressing the memory corruption in the registration code; physical access controls may provide temporary mitigation until patches are deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0119 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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