LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25948: Prototype pollution vulnerability in 'expand-hash' versions 0.1.0 through 1.0.1 allows an attacker to cause...

Prototype pollution vulnerability in 'expand-hash' versions 0.1.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-25948 affects the Node package expand-hash. Listed vulnerable versions can let attacker-controlled input pollute JavaScript object prototypes, causing denial of service and possibly remote code execution. Business urgency depends on whether this dependency is present and reachable from untrusted input.

Executive priority

Prioritize verification now. If the dependency is present in internet-facing or untrusted-input services, treat remediation as urgent because stated impact includes service disruption and possible code execution.

Technical view

The source bundle identifies prototype pollution in expand-hash versions 0.1.0 through 1.0.1. The public description states impact as denial of service with possible remote code execution. No CVSS, CWE, exploit details, or fixed version is provided in the supplied sources.

Likely exposure

Exposure is likely limited to Node.js applications that directly or transitively include expand-hash versions 0.1.0 through 1.0.1 and process untrusted data through it.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Treat exploitation as plausible only where vulnerable expand-hash code is reachable from user-controlled input.

Researcher notes

Evidence is sparse: affected versions and impact are identified, but no CVSS vector, CWE, proof of active exploitation, or fixed release is included. Validation should focus on reachability and dependency presence rather than assuming universal exposure.

Mitigation direction

  • Inventory direct and transitive use of expand-hash in Node dependency manifests and lockfiles.
  • Check vendor or advisory guidance for a fixed or maintained release before upgrading.
  • If no fix is available, remove or replace expand-hash in affected applications.
  • Prevent untrusted input from reaching expand-hash until remediation is complete.
  • Prioritize internet-facing services and APIs that parse user-supplied structured data.

Validation and detection

  • Confirm whether expand-hash versions 0.1.0 through 1.0.1 appear in application dependency trees.
  • Map every identified instance to the service, route, or job that can invoke it.
  • Review whether user-controlled input can flow into expand-hash processing.
  • After remediation, confirm vulnerable versions are absent from lockfiles and deployed artifacts.
  • Run relevant unit and regression tests for affected parsing or data-processing paths.
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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25948 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aexpand-hash0.1.0, 0.1.1, 0.2.1, 0.2.2, 1.0.0, 1.0.1Listed
Weakness

CWE details

No CWE listed

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