ChromeWeb browser · Google
CVE-2025-0996
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 · uneditedInappropriate implementation in Browser UI in Google Chrome on Android prior to 133.0.6943.98 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: High)
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 · high confidenceThis is a URL spoofing vulnerability in Google Chrome for Android where a remote attacker can use a crafted HTML page to manipulate the Omnibox (URL bar) to display misleading information. This allows the attacker to make users believe they are visiting a different website than the one actually loaded.
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 data
ChromeWeb browser
< 133.0.6943.98CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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 Chrome for Android versionOpen Google Chrome on the Android device, tap the three-dot menu, select 'Settings', then tap 'About Chrome' to view the installed version numberAffected if The displayed version is lower than 133.0.6943.98
-
Verify version via chrome://versionIn the Chrome address bar, type 'chrome://version' and press Enter to view detailed version information including the complete version stringAffected if The version string shows a build number below 133.0.6943.98
-
Check for pending updatesOpen the Google Play Store app, search for 'Google Chrome', and check if an update is available or if the app shows 'Open' instead of 'Update'Affected if An update to version 133.0.6943.98 or later is available, indicating the current version is vulnerable
A user is affected if Google Chrome for Android is installed at a version lower than 133.0.6943.98, as this version range contains the URL spoofing flaw in the Omnibox.
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 · scoped133.0.6943.98
Update Google Chrome for Android to version 133.0.6943.98 or later to patch this vulnerability. Organizations should ensure managed devices receive this update through their mobile device management (MDM) solution or enterprise mobility policies.
Chrome Android 133.0.6943.98 or later
- Open Google Play Store on the Android device
- Search for Google Chrome in the app store
- Tap the Update button to install version 133.0.6943.98 or later
- Alternatively, enable 'Auto-update apps' in Play Store settings to ensure Chrome receives future security updates automatically
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0996 — 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-0996 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