Skip to main content
Menu
CVEs

Quasar DOM clobbering denial of service in native-bridge checks

CVE-2026-133233EUVD-2026-130323Published November 19, 2026, updated

2.3LowCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 2.35.3
Who is exposed
Not reported

Summary

Quasar, a web framework, is affected by a DOM clobbering flaw: an attacker can inject HTML elements named Capacitor, cordova, or StatusBar into server-rendered or pre-rendered pages, which makes the app fail to start or breaks some native-bridge calls. The attacker can reach it remotely without logging in, but the victim must take an action such as opening a crafted page.

Written by a model

Original description

Quasar before 2.35.3 contains a DOM clobbering vulnerability that allows attackers to break native wrapper detection by injecting HTML elements named Capacitor, cordova, or StatusBar. Attackers can place markup such as a div with id Capacitor into server-rendered or pre-rendered HTML so app.use(Quasar) throws and the application never mounts, or openURL() and AddressbarColor.set() throw.

What to do

Upgrade to a fixed version: 2.35.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133233 (Quasar before 2.35.3 DOM Clobbering Denial of Service via Native-Bridge Checks), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133233 (entry last updated 2026-11-19):
Affected:
- npm package quasar: fixed in 2.35.3
Fixed versions: 2.35.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133233 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133233 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/quasarframework/quasar/security/advisories/GHSA-6p98-c9vp-9m6w
- https://github.com/quasarframework/quasar/commit/5e7e27e4fe78e9b0f4e3c810d8986e252953d98d
- https://github.com/quasarframework/quasar/releases/tag/quasar-v2.35.3
- https://github.com/quasarframework/quasar/blob/quasar-v2.35.2/ui/src/plugins/private.history/History.js#L53-L60
- https://github.com/quasarframework/quasar
- https://www.vulncheck.com/advisories/quasar-before-2.35.3-dom-clobbering-denial-of-service-via-native-bridge-checks
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133233
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133233"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach12/20quasar: 526.5K downloads a week
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 51 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-133233

Is CVE-2026-133233 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133233?

quasar (npm): before 2.35.3.

Source: cve.now feed data

How do I fix CVE-2026-133233?

Upgrade to a fixed version: 2.35.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.