How severe is GHSA-x7j8-49r8-mr43?

No CVSS score has been assigned to GHSA-x7j8-49r8-mr43 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x7j8-49r8-mr43?

GHSA-x7j8-49r8-mr43 affects the following packages: @nevware21/ts-utils (npm). Ecosystems affected: npm.

How do I fix GHSA-x7j8-49r8-mr43?

Update @nevware21/ts-utils to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7j8-49r8-mr43 is resolved across your whole dependency graph.

How do I detect GHSA-x7j8-49r8-mr43 in my npm dependencies?

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

How do I mitigate GHSA-x7j8-49r8-mr43 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-x7j8-49r8-mr43 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x7j8-49r8-mr43 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-x7j8-49r8-mr43?

GHSA-x7j8-49r8-mr43 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th 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-x7j8-49r8-mr43?

GHSA-x7j8-49r8-mr43 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 GHSA-x7j8-49r8-mr43 published, and has it been updated?

GHSA-x7j8-49r8-mr43 was published on May 21, 2026 and was last updated on September 10, 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-x7j8-49r8-mr43 — @nevware21/ts-utils

GHSA-x7j8-49r8-mr43 is a CWE-1321 vulnerability in @nevware21/ts-utils. A fix is available for @nevware21/ts-utils — see the affected versions and patch details below.

@nevware21/ts-utils: Prototype Pollution in objDeepCopy/objCopyProps via for...in without hasOwnProperty

Also known asCVE-2026-46681

Published

May 21, 2026

Updated

Sep 10, 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

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 GHSA-x7j8-49r8-mr43.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

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

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

@nevware21/ts-utilsnpm

1.5Mdownloads / week

Description

Summary

The _copyProps function in lib/src/object/copy.ts uses for...in to iterate over source object properties without an Object.hasOwnProperty check, and does not filter dangerous keys (proto, constructor, prototype). This allows an attacker to pollute the prototype chain of all objects in the application.

Details

In _copyProps() (copy.ts lines 186-191), the code iterates all enumerable properties including inherited ones and dangerous keys like proto. Any object with a proto key (e.g., from untrusted JSON input) will overwrite the target's prototype.

PoC

const malicious = JSON.parse('{"__proto__": {"polluted": true}}');
objDeepCopy(malicious);
console.log({}.polluted); // true

Suggested Fix

Add objHasOwnProperty check and filter proto, constructor, prototype keys.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@nevware21/ts-utils`	all versions	0.14.0`npm install @nevware21/ts-utils@0.14.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nevware21/ts-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nevware21/ts-utils to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7j8-49r8-mr43 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.

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

This vulnerability is rated as Important. The `@nevware21/ts-utils` library is susceptible to prototype pollution when processing untrusted input, allowing an attacker to modify the prototype chain of objects. This could lead to arbitrary code execution within applications utilizing the affected library, impacting…

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-x7j8-49r8-mr43 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Dev Spaces 3.30	`devspaces/code-rhel9:1787762793`	RHSA-2026:62260

Frequently Asked Questions

## Summary The _copyProps function in lib/src/object/copy.ts uses for...in to iterate over source object properties without an Object.hasOwnProperty check, and does not filter dangerous keys (__proto__, constructor, prototype). This allows an attacker to pollute the prototype chain of all objects in the application. ## Details In _copyProps() (copy.ts lines 186-191), the code iterates all enumerable properties including inherited ones and dangerous keys like __proto__. Any object with a __proto__ key (e.g., from untrusted JSON input) will overwrite the target's prototype. ## PoC ``` const

O3 Security · Impact-Aware SCA

Is GHSA-x7j8-49r8-mr43 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works