express-rate-limit-8.5.2.tgz: 1 vulnerabilities (highest severity is: 5.8)

[mend-for-github-com]

Vulnerable Library - express-rate-limit-8.5.2.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-theme-customization/project/package.json,/tutorials/vonage_video_react_app-feature-config/project/package.json

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (express-rate-limit version)	Remediation Possible**
CVE-2026-54272	Medium	5.8	ip-address-10.2.0.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-54272

Vulnerable Library - ip-address-10.2.0.tgz

A library for parsing IPv4 and IPv6 IP addresses in node and the browser.

Library home page: https://registry.npmjs.org/ip-address/-/ip-address-10.2.0.tgz

Path to dependency file: /tutorials/vonage_video_react_app-theme-customization/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-theme-customization/project/package.json,/tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• express-rate-limit-8.5.2.tgz (Root Library)
  • ❌ ip-address-10.2.0.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Versions 10.1.1 through 10.2.0 are vulnerable to SSRF through misclassification of IPv4-mapped/NAT64 IPv6 addresses. Address6.getType() classifies an address by matching it against a table of known IPv6 special-use prefixes, returning Global unicast when nothing matches. That table had no entry for the IPv4-mapped range (::ffff:0:0/96), so every mapped address fell through to Global unicast; NAT64 addresses matched their own NAT64 … labels. The boolean checks isLoopback, isUnspecified, and isMulticast compared getType() against a fixed label and so returned false, while isLinkLocal and isULA checked only the native IPv6 ranges. The library already exposed isMapped4() and to4(), but did not apply them inside these checks, so a mapped or NAT64 address was never normalized to its embedded IPv4 address before classification. For IPv4-mapped addresses the host OS routes to the IPv4 stack, so the misclassification is reachable on any dual-stack host. For NAT64, the classification bypass is unconditional but end-to-end reachability additionally requires a NAT64/DNS64 gateway in the deployment network.This issue has been fixed in version 10.2.1.

Publish Date: 2026-07-27

URL: CVE-2026-54272

CVSS 3 Score Details (5.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-22jq-vg5j-6vgg

Release Date: 2026-07-27

Fix Resolution: ip-address - 10.2.1