How severe is GHSA-crpf-4hrx-3jrp?

No CVSS score has been assigned to GHSA-crpf-4hrx-3jrp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-crpf-4hrx-3jrp?

GHSA-crpf-4hrx-3jrp affects the following packages: svelte (npm). Ecosystems affected: npm.

How do I fix GHSA-crpf-4hrx-3jrp?

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

How do I detect GHSA-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp?

O3 pinpoints whether GHSA-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp actively exploited in the wild?

No public exploit code has been indexed for GHSA-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp?

GHSA-crpf-4hrx-3jrp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, 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-crpf-4hrx-3jrp?

GHSA-crpf-4hrx-3jrp is classified as CWE-915 (CWE-915). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-crpf-4hrx-3jrp published, and has it been updated?

GHSA-crpf-4hrx-3jrp was published on February 19, 2026 and was last updated on April 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

GHSA-crpf-4hrx-3jrp

Svelte SSR attribute spreading includes inherited properties from prototype chain

Also known asCVE-2026-27125

Published

Feb 19, 2026

Updated

Apr 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk29th percentile+0.35%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦svelte

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

In server-side rendering, attribute spreading on elements (e.g. <div {...attrs}>) enumerates inherited properties from the object's prototype chain rather than only own properties. In environments where Object.prototype has already been polluted — a precondition outside of Svelte's control — this can cause unexpected attributes to appear in SSR output or cause SSR to throw errors. Client-side rendering is not affected.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`svelte`	all versions	5.51.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.51.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp 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-crpf-4hrx-3jrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In server-side rendering, attribute spreading on elements (e.g. `<div {...attrs}>`) enumerates inherited properties from the object's prototype chain rather than only own properties. In environments where `Object.prototype` has already been polluted — a precondition outside of Svelte's control — this can cause unexpected attributes to appear in SSR output or cause SSR to throw errors. Client-side rendering is not affected.

O3 Security · Impact-Aware SCA

Is GHSA-crpf-4hrx-3jrp in your dependencies?

O3 detects GHSA-crpf-4hrx-3jrp 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