How severe is GHSA-m6jq-g7gq-5w3c?

No CVSS score has been assigned to GHSA-m6jq-g7gq-5w3c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m6jq-g7gq-5w3c?

GHSA-m6jq-g7gq-5w3c affects the following packages: @builder.io/qwik-city (npm). Ecosystems affected: npm.

How do I fix GHSA-m6jq-g7gq-5w3c?

Update @builder.io/qwik-city to 1.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6jq-g7gq-5w3c is resolved across your whole dependency graph.

How do I detect GHSA-m6jq-g7gq-5w3c in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @builder.io/qwik-city, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m6jq-g7gq-5w3c if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-m6jq-g7gq-5w3c actively exploited in the wild?

No public exploit code has been indexed for GHSA-m6jq-g7gq-5w3c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m6jq-g7gq-5w3c?

GHSA-m6jq-g7gq-5w3c has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m6jq-g7gq-5w3c?

GHSA-m6jq-g7gq-5w3c is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m6jq-g7gq-5w3c published, and has it been updated?

GHSA-m6jq-g7gq-5w3c was published on February 3, 2026 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Qwik SSR XSS via Unsafe Virtual Node SerializationGHSA-m6jq-g7gq-5w3c

Fix: QwikDev/qwik@fe2d923

GHSA-m6jq-g7gq-5w3c is a Cross-site Scripting (XSS) vulnerability in @builder.io/qwik-city. A fix is available for @builder.io/qwik-city — see the affected versions and patch details below.

Also known asCVE-2026-25148

Published

Feb 3, 2026

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m6jq-g7gq-5w3c.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@builder.io/qwik-citynpm

49Kdownloads / week

Description

Summary

Description A Cross-site Scripting (CWE-79) vulnerability in Qwik.js' server-side rendering virtual attribute serialization allows a remote attacker to inject arbitrary web scripts into server-rendered pages via virtual attributes. Successful exploitation permits script execution in a victim's browser in the context of the affected origin. This affects qwik-city before version 1.19.0. This has been patched in qwik-city version 1.19.0.

Impact

This vulnerability impacts applications that dynamically populate Virtual Node attributes with keys/values that users can influence. Applications that hard-code these keys/values are unaffected.

Qwik doesn't use traditional hydration. Instead, it serializes application state into the HTML so the client can resume execution from the server-rendered output. To support this, Qwik v1 marks component boundaries with HTML comments. SSR builds comment content for Virtual components by concatenating structural attribute names and values without any escaping or quoting. An attacker-controlled key or value can prematurely close the HTML comment and inject arbitrary HTML/JS.

Successful exploitation permits script execution in a victim’s browser in the context of the affected origin. Additionally, because Qwik uses these serialized comment markers for resumability, breaking comment structure can lead to resume/hydration desync and unexpected client-side behavior.

Patches

This has been patched in qwik-city version 1.19.0. Users are strongly encouraged to update to the latest available release.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@builder.io/qwik-city`	all versions	1.19.0`npm install @builder.io/qwik-city@1.19.0`

Affected Products

1 product · 1 configurations

Application

qwikqwik

< 1.19.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @builder.io/qwik-city, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @builder.io/qwik-city to 1.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6jq-g7gq-5w3c is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Summary **Description** A Cross-site Scripting (CWE-79) vulnerability in Qwik.js' server-side rendering virtual attribute serialization allows a remote attacker to inject arbitrary web scripts into server-rendered pages via virtual attributes. Successful exploitation permits script execution in a victim's browser in the context of the affected origin. This affects qwik-city before version 1.19.0. This has been patched in qwik-city version 1.19.0. ### Impact This vulnerability impacts applications that dynamically populate Virtual Node attributes with keys/values that users can influence.

O3 Security · Impact-Aware SCA

Is GHSA-m6jq-g7gq-5w3c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works