CVE-2026-106102 quasarframework CVE debrief

Who should care

Defenders who use the Quasar Framework in their applications should be aware of this vulnerability and take steps to verify the versions of Quasar used in their applications and update to version 2.22.0 or later. They should also review their application's code for any usage of the `useMeta()` composable and ensure that any user-controlled values are properly sanitized.

Why it matters

The Quasar Framework is vulnerable to stored and reflected XSS attacks due to the lack of HTML-entity escaping and attribute-quote escaping in the `getHead()` function. Defenders should prioritize verifying the versions of Quasar used in their applications and updating to version 2.22.0 or later. They should also review their application's code for any usage of the `useMeta()` composable and ensure that any user-controlled values are properly sanitized.

• An attacker could inject malicious HTML code, potentially leading to XSS attacks.
• The vulnerability could be used to steal user data or take control of the user's session.
• The vulnerability could be used to deface or modify the application's pages.
• Defenders need to verify the versions of Quasar used in their applications and update to version 2.22.0 or later.

Technical summary

The Quasar Framework is vulnerable to stored and reflected XSS attacks due to the lack of HTML-entity escaping and attribute-quote escaping in the `getHead()` function. This function is used to serialize meta/link/script/title data collected from the `useMeta()` composable into a literal HTML string, which is then interpolated into the raw HTTP response `<head>` by the production SSR template. The vulnerability is triggered when an attacker-controlled value is passed to the `useMeta()` composable, allowing them to inject malicious HTML code. Defenders should prioritize verifying the versions of Quasar used in their applications and updating to version 2.22.0 or later. They should also review their application's

Defensive priority

Defenders should prioritize verifying the versions of Quasar used in their applications and updating to version 2.22.0 or later. They should also review their application's code for any usage of the `useMeta()` composable and ensure that any user-controlled values are properly sanitized.

Recommended defensive actions

• Verify the versions of Quasar used in your applications and update to version 2.22.0 or later.
• Review your application's code for any usage of the `useMeta()` composable and ensure that any user-controlled values are properly sanitized.
• Implement additional security measures such as Content Security Policy (CSP) to prevent XSS attacks.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability is caused by the lack of HTML-entity escaping and attribute-quote escaping in the `getHead()` function. The `getHead()` function is used to serialize meta/link/script/title data collected from the `useMeta()` composable into a literal HTML string. The vulnerability is triggered when an attacker-controlled value is passed to the `useMeta()` composable, allowing them to inject malicious HTML code.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.