PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-13149 juliangruber CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-06-30T10:16:34.560Z and has not been modified since then. The NVD entry is currently Deferred. This denial of service vulnerability affects brace-expansion through 5.0.6, allowing an attacker to cause significant CPU consumption and event-loop blocking by passing a crafted string to expand(), directly or transitively.

Vendor
juliangruber
Product
brace-expansion
CVSS
HIGH 7.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-30
Original CVE updated
2026-07-08
Advisory published
2026-06-30
Advisory updated
2026-07-08

Who should care

Users of brace-expansion through 5.0.6, operators, platform administrators, vulnerability management teams, and security teams should be aware of this denial of service vulnerability. The expand() function's exponential-time complexity can cause significant CPU consumption and event-loop blocking when processing crafted strings.

Technical summary

The CVE-2026-13149 vulnerability affects brace-expansion through 5.0.6. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker can cause significant CPU consumption and event-loop blocking by passing a crafted string to expand(), directly or transitively. The max option does not mitigate this issue as it bounds the output size rather than the recursion work. Users of brace-expansion should be aware of this denial of service vulnerability.

Defensive priority

High priority should be given to updating brace-expansion to a version beyond 5.0.6 to prevent potential denial of service attacks. Additionally, validating and sanitizing input strings, implementing monitoring, and applying compensating controls can help mitigate the vulnerability.

Recommended defensive actions

  • Update brace-expansion to a version beyond 5.0.6
  • Validate and sanitize input strings to prevent crafted inputs
  • Implement monitoring to detect potential CPU consumption and event-loop blocking
  • Consider applying compensating controls to limit the impact of potential attacks
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail provide information on the vulnerability. However, further analysis is required to fully understand the affected scope and potential impact. The expand() function's exponential-time complexity can cause significant CPU consumption and event-loop blocking when processing crafted strings. Users should verify their deployments and review official advisories for affected scope and vendor guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-13149 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-13149

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-13149 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-13149

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/juliangruber/brace-expansion/commit/c7e33ec13ac1a684c116720843ce24e208611754

    22e2d327-25fe-45d7-9f0c-dcd23b7108df

  • Source reference

    Unverified legacy reference

    URL: https://www.npmjs.com/package/brace-expansion

    22e2d327-25fe-45d7-9f0c-dcd23b7108df

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.