CVE-2026-25047: deepHas provides a test for the existence of a nested object key and optionally returns that key

Q: How do I fix CVE-2026-25047?

deephas: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2026-25047 being exploited?

CVE-2026-25047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-25047 affect?

CVE-2026-25047 affects deephas. Severity is high (CVSS 8.8). deepHas provides a test for the existence of a nested object key and optionally returns that key. A prototype pollution vulnerability exists in version 1.0.7 of the deephas npm package that allows an attacker to modify global object behavio

Q: How urgent is CVE-2026-25047?

Priority 50/100. High severity; Public exploit reference

This month

HIGH 8.8DOWNGRADE

CVE-2026-25047 is a high-severity flaw (CVSS 8.8) affecting deephas. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

deepHas provides a test for the existence of a nested object key and optionally returns that key. A prototype pollution vulnerability exists in version 1.0.7 of the deephas npm package that allows an attacker to modify global object behavior. This issue was fixed in version 1.0.8.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-1321
Published	2026-01-29
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: sharpred

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-29 22:15 UTCPublished CVE record published
2026-06-17 10:24 UTCUpdated Record last modified

sharpred deephas DOWNGRADE

Affected: 1.0.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.7

1. Check installed version

npm ls deephas

2. No fixed release: DOWNGRADE to a release before 1.0.7

npm view deephas versions npm install deephas@"<1.0.7"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: deephas 1.0.7 - Prototype Pollution

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-25047?

deephas: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-25047 being exploited?

CVE-2026-25047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-25047 affect?

CVE-2026-25047 affects deephas. Severity is high (CVSS 8.8). deepHas provides a test for the existence of a nested object key and optionally returns that key. A prototype pollution vulnerability exists in version 1.0.7 of the deephas npm package that allows an attacker to modify global object behavio

How urgent is CVE-2026-25047?

Priority 50/100. High severity; Public exploit reference

Software pages

npm packages vulnerabilities

References

← Back to latest CVEs