LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25047: deepHas vulnerable to Prototype Pollution via constructor.prototype

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.

CriticalCVSS 9.4Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25047 is a critical prototype pollution issue in the deephas npm package. If an application processes attacker-controlled object paths through the vulnerable code, an attacker may alter JavaScript object behavior broadly. The sources say the issue is fixed in version 1.0.8, but the affected-version statement is inconsistent.

Executive priority

Prioritize assessment because the CVSS score is critical and the bug class can have broad application impact. Treat as urgent for internet-facing services using deephas with untrusted input, while noting there is no sourced evidence of active exploitation.

Technical view

The advisory describes prototype pollution via constructor.prototype in deephas, mapped to CWE-1321, with CVSS 4.0 score 9.4. The CVE description says version 1.0.7 is vulnerable and 1.0.8 fixes it. The affected list in the bundle says <1.0.7, which conflicts with that description.

Likely exposure

Exposure is likely limited to Node.js applications or build tooling that include the deephas npm package and pass untrusted input into nested-key checks. Transitive dependency exposure should be assessed through dependency inventory and lockfiles.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Practical risk depends on whether attacker-controlled property paths can reach deephas in the application. Prototype pollution can affect confidentiality, integrity, and availability depending on application behavior.

Researcher notes

The main uncertainty is affected-version scope: the description names 1.0.7 as vulnerable and 1.0.8 as fixed, while the affected entry says <1.0.7. Use the GitHub advisory and commit as primary validation points before making enforcement rules.

Mitigation direction

  • Upgrade deephas to version 1.0.8 where supported by the vendor advisory.
  • Review dependency trees for direct and transitive deephas usage.
  • If upgrade is blocked, check vendor guidance for supported workarounds.
  • Restrict untrusted input from reaching nested object path checks where feasible.

Validation and detection

  • Confirm installed deephas versions in package manifests and lockfiles.
  • Check whether deephas is direct or transitive in deployed applications.
  • Verify production builds use version 1.0.8 or later if applicable.
  • Review code paths for user-controlled keys passed to deephas functionality.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25047 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 4.0CriticalCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.4Critical
CVSS 4.0 vector shape for CVE-2026-25047Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
sharpreddeepHas< 1.0.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.