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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qgvg-pr8v-6rr3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qgvg-pr8v-6rr3?

O3 pinpoints whether GHSA-qgvg-pr8v-6rr3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 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

GHSA-qgvg-pr8v-6rr3

Fix: sveltejs/svelte@0298e97

GHSA-qgvg-pr8v-6rr3 is a Cross-site Scripting (XSS) vulnerability in svelte. O3 Security confirms whether GHSA-qgvg-pr8v-6rr3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Svelte: XSS via HTML Comment Injection in SSR Error Boundary Hydration Markers

Also known asCVE-2026-27902

Published

Feb 26, 2026

Updated

Feb 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

sveltenpm

5.4Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for svelte. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qgvg-pr8v-6rr3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qgvg-pr8v-6rr3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-qgvg-pr8v-6rr3 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works