ChromeWeb browser · Google
CVE-2026-8561
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 · uneditedIncorrect security UI in Fullscreen in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to perform UI spoofing 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 confidenceUI spoofing vulnerability in Google Chrome's fullscreen mode allows a remote attacker to display misleading or fake UI elements via a crafted HTML page, potentially tricking users into believing they're interacting with legitimate content.
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
< 148.0.7778.168CVSS 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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
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://version in the Chrome address bar or right-click the Chrome shortcut and select 'About Google Chrome'Affected if The version shown is earlier than 148.0.7778.168 (e.g., 148.0.7778.100, 148.0.0.0, or any version below 148.0.7778.168)
-
Verify fullscreen mode is accessibleConfirm that the Chrome browser supports fullscreen functionality - press F11 or click the fullscreen icon in Chrome to enter fullscreen modeAffected if Fullscreen mode is available and functional in the browser
-
Identify exposure to untrusted contentReview browser usage patterns - determine if users commonly open HTML files or visit untrusted websites that could trigger fullscreen modeAffected if Users can be persuaded to open or interact with crafted HTML pages in fullscreen mode
If Google Chrome version is lower than 148.0.7778.168 and users can encounter untrusted content in fullscreen mode, the environment is affected by this UI spoofing vulnerability.
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 · scoped148.0.7778.168
Update Google Chrome to version 148.0.7778.168 or later. Users should be advised to keep browsers patched and be cautious of fullscreen content from untrusted sources.
148.0.7778.168 (Chrome stable)
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 148.0.7778.168, download Chrome version 148.0.7778.168 or later from the official Google Chrome download page at google.com/chrome
- Install the updated Chrome version
- Restart Chrome to complete the update
- Verify the installed version is 148.0.7778.168 or later by visiting chrome://settings/help again
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8561 — 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-8561 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