CVE-2025-36904
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 · uneditedWLAN in Android before 2025-09-05 on Google Pixel devices allows elevation of privilege, aka A-396458384.
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 confidenceWLAN component in Android contains an elevation of privilege vulnerability affecting Google Pixel devices prior to the September 2025 security patch. The flaw allows an attacker to gain elevated privileges through the WiFi stack, likely due to improper input validation or privilege boundary issues within the WLAN subsystem.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Confirm device is a Google PixelCheck the device model in Settings > About Phone > Model or look for 'Pixel' branding on the deviceAffected if Device is NOT a Google Pixel (this CVE specifically affects Pixel devices)
-
Check Security Patch LevelNavigate to Settings > About Phone > Security Patch Level and note the date displayedAffected if Security Patch Level is earlier than 2025-09-05 (September 5, 2025)
-
Verify automatic updates are enabledCheck Settings > Security & Privacy > Security Update > Automatic security updates is set to allow updatesAffected if Automatic updates are disabled and manual patch verification shows outdated level
A Google Pixel device with Security Patch Level before September 5, 2025 is affected by this vulnerability in the WLAN component.
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.
dbcve · scopedApply Android security patch level 2025-09-05 or later to affected Google Pixel devices. Users should ensure automatic security updates are enabled and verify their patch level in Settings > About Phone > Security Patch Level.
Google Pixel devices - Android with September 2025 Security Patch Level (or later)
- 1. Check current Android security patch level on the Google Pixel device: Settings > About Phone > Android version > Security patch level
- 2. Ensure the device is connected to Wi-Fi or mobile data with battery sufficiently charged
- 3. Navigate to Settings > System > Software Update (or Settings > Security & privacy > System updates on newer Android versions)
- 4. Tap 'Check for updates' to fetch the latest available update
- 5. If an update is available, review the update details to confirm it includes the September 2025 Android Security Bulletin (or later)
- 6. Tap 'Download and install' to apply the update
- 7. Wait for the update to download, verify, and install - the device will restart automatically
- 8. After reboot, verify the new security patch level in Settings > About Phone > Android version reflects September 2025 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36904 — 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-2025-36904 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