Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-14257] Denial of Service via memory exhaustion in expand function

This high-severity Red Hat Linux advisory covers CVE-2026-14257.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-14257 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Denial of Service via memory exhaustion in expand() function. Red Hat rates this important (CVSS 7.5).

Weakness: CWE-770. Red Hat lists fixing advisory RHSA-2026:45381 with package nodejs26-main-26.5.0-1.4.hum1, grafana12-4-main-12.4.6-0.4.hum1, nodejs22-main-22.23.1-2.3.hum1, nodejs24-main-24.18.0-0.5.hum1.

Affected versions
  • 5.0.7

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • nodejs26-main-26.5.0-1.4.hum1
  • grafana12-4-main-12.4.6-0.4.hum1
  • nodejs22-main-22.23.1-2.3.hum1
  • nodejs24-main-24.18.0-0.5.hum1
  • nodejs24-main-24.18.1-0.2.1.hum1
  • nodejs26-main-26.7.0-1.5.2.hum1
  • RHSA-2026:45381

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Do not pass untrusted or user-controlled input to brace-expansion's expand() function or to libraries that use it for glob pattern matching (such as minimatch or glob). Validate and sanitize any brace patterns before expansion. Where possible, upgrade to brace-expansion 1.1.17, 2.1.3, 3.0.3, or 5.0.8 which add a maxLength option that bounds accumulated output. As an additional defense-in-depth measure, enforce memory limits on Node.js processes using operating system resource controls such as cgroups or Kubernetes resource limits (spec.containers[].resources.limits.memory) to prevent a single process from exhausting system memory and causing a wider outage.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.