ChromeWeb browser · Google
CVE-2025-5281
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 BFCache in Google Chrome prior to 137.0.7151.55 allowed a remote attacker to potentially obtain user information via a crafted HTML page. (Chromium security severity: Medium)
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 Google Chrome's BFCache (Back-Forward Cache) implementation prior to version 137.0.7151.55 allows a remote attacker to potentially obtain user information through a specially crafted HTML page. The BFCache stores a complete page snapshot for faster navigation, and this implementation flaw could leak sensitive data from cached pages.
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
< 137.0.7151.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
- 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.
-
Check installed Chrome versionOpen chrome://settings/help or go to Menu > Help > About Google Chrome to view the current version numberAffected if The version shown is less than 137.0.7151.55 (e.g., 136.x.x.x or earlier)
-
Confirm Chrome channelIn chrome://settings/help, verify if the browser is on Stable, Beta, or another channel - the fix is deployed via Stable channelAffected if Browser is on Stable channel but version remains below 137.0.7151.55 after checking for updates
-
Verify BFCache is activeThe BFCache (Back-Forward Cache) is enabled by default in Chrome. Visit any HTTP site, navigate to a second page, then use the browser back button - if the page loads instantly without re-requesting, BFCache is activeAffected if BFCache is functioning and the Chrome version is below 137.0.7151.55
You are affected if your Chrome version is below 137.0.7151.55 and BFCache (back-forward cache) is enabled in your browser, as the vulnerability lies in the BFCache implementation.
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 · scoped137.0.7151.55
Update Google Chrome to version 137.0.7151.55 or later. Organizations should deploy the browser update via their patch management infrastructure and verify complete coverage.
Chrome 137.0.7151.55 (or later stable release)
- Open Google Chrome browser
- Click on the three-dot menu in the top-right corner
- Select 'Help' then 'About Google Chrome'
- The browser will automatically check for updates
- If version 137.0.7151.55 or later is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
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
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5281 — 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-5281 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