CVE-2026-0151
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 IntfGraphCreate of intfgraph.c, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution 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 integer overflow in the IntfGraphCreate function in intfgraph.c causes an out-of-bounds write vulnerability. This can be exploited remotely without authentication or user interaction to achieve arbitrary code execution.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the Android versionCheck the Android version on the device through Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The device runs any version of Android, as all versions are affected according to the CVE scope
-
Determine if intfgraph component is presentSearch for the intfgraph.c file or related library files on the system. This may be part of a graphics, media, or interface-related module. Use 'find / -name '*intfgraph*' 2>/dev/null' via ADB root shell if availableAffected if The vulnerable IntfGraphCreate function exists in the system's code base
-
Check for indicators of exploitationReview system logs and security audit logs for suspicious out-of-bounds memory writes, unexpected process crashes, or unauthorized network activity. Use 'dmesg' and check '/var/log/' for relevant entriesAffected if Log entries show memory corruption, unexpected privilege escalation, or anomalous code execution patterns
-
Identify the product containing intfgraph.cDetermine what product, library, or service includes the intfgraph.c component. This may be a vendor-specific graphics or interface framework. Check installed packages and system servicesAffected if The vulnerable code is part of an actively used component on the device
-
Review network exposureAssess whether the device or its services are exposed to network access. Check firewall rules, open ports, and network service configurationsAffected if The device has network-facing services that could trigger remote exploitation without user interaction
-
Compare against vendor advisoriesCheck the device manufacturer's security advisory pages or support documentation for mentions of CVE-2026-0151 and specific patch statusAffected if The vendor has not issued a patch for this CVE and the device remains vulnerable
A user is affected if they run any version of Android that contains the vulnerable IntfGraphCreate function in intfgraph.c, particularly if the device has network exposure and lacks vendor patches for this vulnerability.
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 patches when available; until then, minimize network exposure of affected systems and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0151 — 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-0151 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