Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-95405

No exploitation reported by the sources we read.

  • Published2026-11-10
  • WeaknessCWE-119

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In acquireMemory of bt_bqr_offload.cc, there is a possible way to trigger an out of bounds write via a buffer size underflow due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Timeline

dates in UTC
  1. 2026-11-1019:22CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As Google_Devices, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Androidother versions: not affected
    Affected
    • = Android kernelno fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • :unknown:Androidfrom Pixel-family specific:0 · fixed in Pixel-family specific:2026-11-05

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-10
Last Modified
2026-11-12
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-7x9j-5665-wwm9

Frequently asked questions

What is CVE-2026-95405?

In acquireMemory of bt_bqr_offload.cc, there is a possible way to trigger an out of bounds write via a buffer size underflow due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Is CVE-2026-95405 actively exploited?

Active exploitation of CVE-2026-95405 has not been confirmed. Its EPSS score was 0.1% on 2026-11-11, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-95405?

CVE-2026-95405 has a CVSS v3 base score of 8.4 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running :unknown:? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record