ChromeWeb browser · Google
CVE-2026-5901
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 · uneditedInsufficient policy enforcement in DevTools in Google Chrome prior to 147.0.7727.55 allowed an attacker who convinced a user to install a malicious extension to bypass enterprise host restrictions for cookie modification via a crafted Chrome Extension. (Chromium security severity: Low)
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 confidenceInsufficient policy enforcement in Chrome DevTools allowed a malicious extension to bypass enterprise host restrictions for cookie modification. The vulnerability existed in versions prior to 147.0.7727.55 and required user interaction to install the malicious extension.
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
< 147.0.7727.55CVSS 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 installed Chrome versionNavigate to chrome://settings/help or use 'Google Chrome > About Google Chrome' menu to view the installed version numberAffected if The displayed version is lower than 147.0.7727.55
-
Review installed extensionsNavigate to chrome://extensions/ and examine all installed extensions. Look for any unknown, untrusted, or recently installed extensions that you did not intentionally installAffected if Any extension is present that was not approved by your organization or that you do not recognize
-
Check extension policy settingsInspect enterprise policy settings for extensions by viewing chrome://policy or checking local policy files for ExtensionInstallForcelist, ExtensionInstallBlocklist, or similar extension control policiesAffected if Policies allow installation of extensions without organizational approval or lack restrictive extension controls
-
Verify cookie access restrictionsUse DevTools (F12) to attempt cookie inspection on a known enterprise-managed host. Check if enterprise policies properly block unauthorized cookie modificationAffected if Cookie modification is possible on enterprise hosts where such access should be restricted by policy
You are affected if your Chrome version is below 147.0.7727.55 AND you have untrusted extensions installed that could bypass enterprise cookie 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 · scoped147.0.7727.55
Update Chrome to version 147.0.7727.55 or later, and enforce enterprise extension policies to prevent installation of untrusted extensions.
Chrome version 147.0.7727.55 or later
- 1. Open Google Chrome on the target machine
- 2. Navigate to Chrome Settings (three-dot menu > Settings)
- 3. Click on 'About Chrome' in the left sidebar
- 4. Chrome will automatically check for updates
- 5. If an update is available, click 'Update Google Chrome'
- 6. Restart the browser to complete the update
- 7. Verify the version by returning to 'About Chrome' and confirming the version is 147.0.7727.55 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5901 — 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-5901 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