How severe is GHSA-rcqx-6q8c-2c42?

No CVSS score has been assigned to GHSA-rcqx-6q8c-2c42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rcqx-6q8c-2c42?

GHSA-rcqx-6q8c-2c42 affects the following packages: svelte (npm). Ecosystems affected: npm.

How do I fix GHSA-rcqx-6q8c-2c42?

Update svelte to 5.55.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcqx-6q8c-2c42 is resolved across your whole dependency graph.

How do I detect GHSA-rcqx-6q8c-2c42 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-rcqx-6q8c-2c42 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-rcqx-6q8c-2c42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rcqx-6q8c-2c42 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-rcqx-6q8c-2c42?

GHSA-rcqx-6q8c-2c42 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-rcqx-6q8c-2c42?

GHSA-rcqx-6q8c-2c42 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-rcqx-6q8c-2c42 published, and has it been updated?

GHSA-rcqx-6q8c-2c42 was published on May 14, 2026 and was last updated on June 9, 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

GHSA-rcqx-6q8c-2c42 — svelte

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

Svelte Vulnerable to XSS via DOM Clobbering of Internal Framework State

Also known asCVE-2026-42573

Published

May 14, 2026

Updated

Jun 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 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-rcqx-6q8c-2c42.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% 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

6.8Mdownloads / week

Description

Svelte was vulnerable to DOM clobbering of its internal framework state on elements, potentially leading to XSS attacks.

You are vulnerable if all of the following is true:

you are using attribute spreading on a form element
you are using attribute spreading or allow a dynamic value for the name attribute on an input or button element within that form
both of these are simultaneously user-controllable

<form {...spread1}>
  <input {...spread2}>
</form>

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`svelte`	all versions	5.55.7`npm install svelte@5.55.7`

Affected Products

1 product · 1 configurations

Application

sveltesvelte

< 5.55.7

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.55.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcqx-6q8c-2c42 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Severity: Important This issue is classified as Important severity for deployments where untrusted content can influence Svelte-rendered markup, because: - Conditions for Exploitation: The flaw is a DOM clobbering issue in the Svelte framework. Exploitation requires an application to render user-influenced markup…

Workaround published by Red Hat

For Red Hat build of Podman Desktop 1.0 and 1.1, no mitigation or dependency update is required. These streams are not affected; the bundled Svelte runtime is not exposed to adversary-controlled input in a way that enables this DOM clobbering flaw. Other products or components that embed Svelte in a context where untrusted markup can reach vulnerable spread patterns should plan to update the Svelte dependency to version 5.55.7 or later when applicable to their shipping model.

Source: Red Hat security advisory for GHSA-rcqx-6q8c-2c42 (CC BY 4.0)

Frequently Asked Questions

Svelte was vulnerable to DOM clobbering of its internal framework state on elements, potentially leading to XSS attacks. You are vulnerable if all of the following is true: - you are using attribute spreading on a form element - you are using attribute spreading or allow a dynamic value for the `name` attribute on an input or button element within that form - both of these are simultaneously user-controllable ```svelte <form {...spread1}> <input {...spread2}> </form> ```

O3 Security · Impact-Aware SCA

Is GHSA-rcqx-6q8c-2c42 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works