How severe is GHSA-qgvg-pr8v-6rr3?

No CVSS score has been assigned to GHSA-qgvg-pr8v-6rr3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qgvg-pr8v-6rr3?

GHSA-qgvg-pr8v-6rr3 affects the following packages: svelte (npm). Ecosystems affected: npm.

How do I fix GHSA-qgvg-pr8v-6rr3?

Update svelte to 5.53.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qgvg-pr8v-6rr3 is resolved across your whole dependency graph.

How do I detect GHSA-qgvg-pr8v-6rr3 in my npm dependencies?

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

How do I mitigate GHSA-qgvg-pr8v-6rr3 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-qgvg-pr8v-6rr3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qgvg-pr8v-6rr3 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-qgvg-pr8v-6rr3?

GHSA-qgvg-pr8v-6rr3 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th 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-qgvg-pr8v-6rr3?

GHSA-qgvg-pr8v-6rr3 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-qgvg-pr8v-6rr3 published, and has it been updated?

GHSA-qgvg-pr8v-6rr3 was published on February 26, 2026 and was last updated on February 26, 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

Svelte: XSS via HTML Comment Injection in SSR Error Boundary Hydration MarkersGHSA-qgvg-pr8v-6rr3

Fix: sveltejs/svelte@0298e97

GHSA-qgvg-pr8v-6rr3 is a Cross-site Scripting (XSS) vulnerability in svelte. A fix is available for svelte — see the affected versions and patch details below.

Also known asCVE-2026-27902

Published

Feb 26, 2026

Updated

Feb 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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-qgvg-pr8v-6rr3.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% 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.

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

sveltenpm

9.4Mdownloads / week

Description

Svelte performance oriented web framework. Prior to version 5.53.5, errors from transformError were not correctly escaped prior to being embedded in the HTML output, causing potential HTML injection and XSS if attacker-controlled content is returned from transformError. Version 5.53.5 fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`svelte`	≥ 5.53.0&&< 5.53.5	5.53.5`npm install svelte@5.53.5`

Affected Products

1 product · 1 configurations

Application

sveltesvelte

≥ 5.53.0 && < 5.53.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for svelte, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update svelte to 5.53.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qgvg-pr8v-6rr3 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

Errors from `transformError` were not correctly escaped prior to being embedded in the HTML output, causing potential HTML injection and XSS if attacker-controlled content is returned from `transformError`.

O3 Security · Impact-Aware SCA

Is GHSA-qgvg-pr8v-6rr3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works