dbcve.org
CWE-451Weakness · CWE-451

CVE-2026-45150

MEDIUM · 6.3 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 · unedited
Zen is a firefox-based browser. Prior to 1.19.13b, Zen Browser did not provide a persistent, clearly visible security notification when a webpage entered fullscreen mode, allowing an attacker-controlled page to hide the real browser UI and origin information, imitate a trusted website UI, and combine with long-domain URL eliding to spoof a trusted origin for phishing and credential theft. This issue is fixed in version 1.19.13b.

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 confidence

Zen Browser versions prior to 1.19.13b lacked a persistent, clearly visible security notification when webpages entered fullscreen mode. This allowed attacker-controlled pages to obscure the browser UI and origin information, enabling UI impersonation of trusted sites combined with URL elision for origin spoofing in phishing attacks.

MitigationUpgrade to Zen Browser version 1.19.13b or later, which implements persistent fullscreen security notifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zen Browser version
    Navigate to zen://version in the address bar or go to Help > About Zen Browser to display the installed version number
    Affected if The displayed version is earlier than 1.19.13b (for example, 1.19.12, 1.18.x, or earlier)
  2. Compare version against the fixed release
    Locate the version number displayed (format typically shows as major.minor.patch such as 1.19.12b) and compare numerically to 1.19.13b
    Affected if The version is 1.19.13b or any build prior to 1.19.13b, as these releases lack the persistent fullscreen notification feature
  3. Verify fullscreen notification presence (optional confirmation)
    Open any webpage, trigger fullscreen mode (press F11 or use the fullscreen API), and observe whether a persistent security indicator showing the current origin/URL remains visible overlay on the screen
    Affected if No persistent notification is visible in fullscreen mode, confirming the vulnerability is present even if the exact version cannot be verified

A user is affected if their installed Zen Browser version is below 1.19.13b, meaning the browser lacks the persistent fullscreen security notification that prevents UI impersonation attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Zen Browser version 1.19.13b or later, which implements persistent fullscreen security notifications.

Recommended fix High confidence

1.19.13b

  1. Check current Zen Browser version by navigating to about:support or looking in the browser menu (Help > About Zen)
  2. Download Zen Browser version 1.19.13b or later from the official repository (github.com/zen-browser/desktop)
  3. Install the updated version, following standard installation procedures for your operating system
  4. Restart the browser after installation completes
  5. Verify the fix by entering fullscreen mode on any website - the browser should now display a persistent security notification indicating the page is in fullscreen mode

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45150 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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