How severe is CVE-2024-36580?

No CVSS score has been assigned to CVE-2024-36580 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-36580?

CVE-2024-36580 affects the following packages: @cdr0/sg (npm). Ecosystems affected: npm.

How do I fix CVE-2024-36580?

The records we use list no patched version of @cdr0/sg for CVE-2024-36580. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2024-36580 in my npm dependencies?

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

How do I mitigate CVE-2024-36580 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.

Is CVE-2024-36580 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-36580 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 CVE-2024-36580?

CVE-2024-36580 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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 CVE-2024-36580?

CVE-2024-36580 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-36580 published, and has it been updated?

CVE-2024-36580 was published on June 17, 2024 and was last updated on June 17, 2024. 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

CVE-2024-36580 — @cdr0/sg

CVE-2024-36580 is a CWE-1321 vulnerability in @cdr0/sg. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

@cdr0/sg Prototype Pollution

Published

Jun 17, 2024

Updated

Jun 17, 2024

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-36580.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

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

@cdr0/sgnpm

20downloads / week

Description

A Prototype Pollution issue in cdr0 sg 1.0.10 allows an attacker to execute arbitrary code.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@cdr0/sg`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @cdr0/sg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of @cdr0/sg for CVE-2024-36580. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

Frequently Asked Questions

A Prototype Pollution issue in cdr0 sg 1.0.10 allows an attacker to execute arbitrary code.

O3 Security · Impact-Aware SCA

Is CVE-2024-36580 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works