Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-106107 – HTML/Script Injection via Unsanitized SSR Nonce – Quasar Framework (@quasar/app-vi

Be the first to know when new zero-days emerge:

Summary

CVE-2026-106107 is an HTML/markup injection vulnerability in the Quasar Framework’s @quasar/app-vite build tooling, affecting server-side rendering (SSR) and static site generation (SSG) output. Multiple rendering paths interpolate the ssrContext.nonce value directly into quoted HTML attributes without sanitization, allowing an attacker-influenced nonce value to break out of the attribute and inject additional markup into the rendered page. The issue carries a CVSS v4.0 base score of 8.3 (High).

Technical details

  • Root cause: Several @quasar/app-vite SSR/SSG rendering paths — including development and production SSR, SSG output, critical CSS injection, store-state script tags, and Vue Devtools integration — write ssrContext.nonce directly into quoted HTML attributes without escaping or validating its contents.
  • Trigger conditions: Exploitation requires an application to derive or override the nonce value from a source an attacker can influence (e.g., request data or another untrusted input) rather than using a properly generated cryptographic nonce. Applications that only ever assign cryptographically generated base64/base64url nonces are not affected, since those formats cannot contain the quote/delimiter characters needed to break out of the attribute.
  • Attack vector: Network — exploitation occurs through the rendered HTML response served to clients, requiring no prior authentication but depending on application-level attack complexity (an attacker must be able to influence the nonce source).
  • Impact: A successful attack lets the attacker terminate the nonce attribute and inject additional HTML attributes or markup into the server-rendered or statically generated page, which can lead to cross-site scripting (XSS) or other HTML injection effects against users of the affected application.

Affected software

  • quasar (Quasar Framework core): versions prior to 2.23.4
  • @quasar/app-vite: versions prior to 3.3.0

Severity

  • CVSS v4.0 Base Score: 8.3 (High)
  • Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
  • Associated weaknesses: CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-site Scripting), CWE-116 (Improper Encoding or Escaping of Output)

Mitigation and recommended actions

  • Immediate: Upgrade @quasar/app-vite to version 3.3.0 or later (and the quasar package to 2.23.4 or later), which centralizes nonce handling across all affected rendering paths, validates that nonce values are non-empty base64/base64url strings, and HTML-encodes the value before it is written into attributes.
  • If immediate patching is not possible: Ensure any custom nonce value used in SSR/SSG rendering is generated exclusively via a cryptographically secure base64 or base64url random generator, and never derived from or overridden by request data or other attacker-influenced input, since such values cannot contain the delimiter characters required to break out of the attribute context.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge