How severe is GHSA-h7h7-mm68-gmrc?

No CVSS score has been assigned to GHSA-h7h7-mm68-gmrc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h7h7-mm68-gmrc?

GHSA-h7h7-mm68-gmrc affects the following packages: svelte (npm). Ecosystems affected: npm.

How do I fix GHSA-h7h7-mm68-gmrc?

Update svelte to 5.51.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h7h7-mm68-gmrc is resolved across your whole dependency graph.

How do I detect GHSA-h7h7-mm68-gmrc 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-h7h7-mm68-gmrc 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-h7h7-mm68-gmrc actively exploited in the wild?

No public exploit code has been indexed for GHSA-h7h7-mm68-gmrc 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-h7h7-mm68-gmrc?

GHSA-h7h7-mm68-gmrc has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th 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-h7h7-mm68-gmrc?

GHSA-h7h7-mm68-gmrc 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-h7h7-mm68-gmrc published, and has it been updated?

GHSA-h7h7-mm68-gmrc was published on February 19, 2026 and was last updated on February 23, 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 affected by XSS in SSR `<option>` elementGHSA-h7h7-mm68-gmrc

GHSA-h7h7-mm68-gmrc 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-27119

Published

Feb 19, 2026

Updated

Feb 23, 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-h7h7-mm68-gmrc.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% 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.5Mdownloads / week

Description

svelte performance oriented web framework. From 5.39.3, <=5.51.4, in certain circumstances, the server-side rendering output of an <option> element does not properly escape its content, potentially allowing HTML injection in the SSR output. Client-side rendering is not affected. This vulnerability is fixed in 5.51.5.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`svelte`	≥ 5.39.3&&< 5.51.5	5.51.5`npm install svelte@5.51.5`

Affected Products

1 product · 1 configurations

Application

sveltesvelte

≥ 5.39.3 && < 5.51.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.51.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h7h7-mm68-gmrc 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 HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-h7h7-mm68-gmrc (CC BY 4.0)

Frequently Asked Questions

In certain circumstances, the server-side rendering output of an `<option>` element does not properly escape its content, potentially allowing HTML injection in the SSR output. Client-side rendering is not affected.

O3 Security · Impact-Aware SCA

Is GHSA-h7h7-mm68-gmrc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works