How severe is GHSA-897m-rjf5-jp39?

GHSA-897m-rjf5-jp39 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-897m-rjf5-jp39?

GHSA-897m-rjf5-jp39 affects the following packages: copy-props (npm). Ecosystems affected: npm.

How do I fix GHSA-897m-rjf5-jp39?

Update copy-props to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-897m-rjf5-jp39 is resolved across your whole dependency graph.

How do I detect GHSA-897m-rjf5-jp39 in my npm dependencies?

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

How do I mitigate GHSA-897m-rjf5-jp39 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 GHSA-897m-rjf5-jp39 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-897m-rjf5-jp39, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-897m-rjf5-jp39?

GHSA-897m-rjf5-jp39 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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.

When was GHSA-897m-rjf5-jp39 published, and has it been updated?

GHSA-897m-rjf5-jp39 was published on January 6, 2022 and was last updated on January 14, 2025. 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

HIGH severity

Prototype Pollution in copy-propsGHSA-897m-rjf5-jp39

HIGHFix: gulpjs/copy-props#7

GHSA-897m-rjf5-jp39 is a high-severity (CVSS 7.3) vulnerability in copy-props. 2 public exploit references exist, so weaponization risk is real. A fix is available for copy-props — see the affected versions and patch details below.

Also known asCVE-2020-28503

Published

Jan 6, 2022

Updated

Jan 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-897m-rjf5-jp39 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

📦copy-props

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

The package copy-props before 2.0.5 are vulnerable to Prototype Pollution via the main functionality.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`copy-props`	all versions	2.0.5`npm install copy-props@2.0.5`

Affected Products

1 product · 1 configurations

Application

copy-propsgulpjs

< 2.0.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The package copy-props before 2.0.5 are vulnerable to Prototype Pollutio…

snyk.ioNVDMar 2021

The package copy-props before 2.0.5 are vulnerable to Prototype Pollutio…

snyk.ioNVDMar 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copy-props, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update copy-props to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-897m-rjf5-jp39 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.

Frequently Asked Questions

The package copy-props before 2.0.5 are vulnerable to Prototype Pollution via the main functionality.

O3 Security · Impact-Aware SCA

Is GHSA-897m-rjf5-jp39 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works