ChromeWeb browser · Google
CVE-2026-13822
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 Extensions in Google Chrome on Android prior to 150.0.7871.47 allowed an attacker who convinced a user to install a malicious extension to bypass same origin policy via a crafted Chrome Extension. (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 confidenceA vulnerability in Chrome's extension system on Android allowed malicious extensions to bypass Same Origin Policy restrictions. The issue stemmed from inappropriate implementation in the Extensions component, enabling a crafted extension to make cross-origin requests that should have been blocked.
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
< 150.0.7871.47CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 the Chrome version on AndroidOpen Chrome on the Android device, navigate to chrome://version or go to Settings > About Chrome to view the installed version numberAffected if The displayed version is below 150.0.7871.47
-
Verify the platform is AndroidConfirm the browser is running on an Android device (phone or tablet) rather than iOS, Windows, macOS, or LinuxAffected if The browser is Chrome on a non-Android platform - this CVE does not apply
-
Check for installed extensionsIn Chrome on Android, go to chrome://extensions or access through Settings > Extensions to see if any extensions are enabledAffected if No extensions are installed or all extensions are disabled - the attack surface is reduced but the vulnerability still exists in the code
-
Confirm Same Origin Policy bypass potentialReview installed extensions - if any extension has broad permissions or was installed from untrusted sources, it could potentially exploit this vulnerabilityAffected if Extensions with elevated permissions or from unknown sources are present on an affected version
You are affected if Chrome on your Android device is version 150.0.7871.47 or lower and has any extensions enabled, as the vulnerability allows malicious extensions to bypass Same Origin Policy restrictions.
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 · scoped150.0.7871.47
Update Google Chrome for Android to version 150.0.7871.47 or later. Organizations should review extension installation policies and consider restricting extension installations to trusted sources only.
Chrome Android 150.0.7871.47 or later
- Open Google Play Store on the Android device
- Search for 'Google Chrome' or locate it in your installed apps
- Update Google Chrome to the latest available version
- Alternatively, go to Settings > Apps > Google Chrome > Updates and check for updates
- Ensure the updated version is 150.0.7871.47 or later
- After updating, verify the version in Chrome by navigating to chrome://version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- 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-13822 — 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-13822 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