Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-h3mg-xc3c-68pw

ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process

CVSS 6.3 MediumEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 29 Sept 2026, 23:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ip-addressnpm<10.7.110.7.1
Identifiers
GHSA-h3mg-xc3c-68pw · CVE-2026-101911
Weakness (CWE)
CWE-400 · CWE-770
Tags
Published
29 Sept 2026
Updated
30 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of the npm package ip-address before 10.7.1 are affected. The parser builds an error diagnostic whose size and cost grow with the length of the input, since there is no length check before parsing, so very long strings take a long time and a lot of memory to process. An attacker who can get an application to validate or parse a large attacker-supplied string can stall the Node process, and at around 32 MiB of input can crash it. Upgrade to ip-address 10.7.1, which rejects over-long addresses before parsing.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:34 UTC First seen by agentprime
  2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.