Juliangruber maintains a narrow, focused toolkit centered on the brace-expansion parsing library, a utility embedded in Node.js tooling and shell-scripting contexts where string-expansion logic is fundamental to operation. The observed vulnerability pattern reflects resource-consumption weaknesses characteristic of parsing-heavy components that process untrusted or large input payloads. Current vulnerability counts, severity distribution, and exploitation status are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Juliangruber over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-13149HIGH brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace g | Jun 30, 2026 | 7.7 | 37 | NO | NO |
CVE-2026-45149HIGH The brace-expansion library generates arbitrary strings containing a common prefix and suffix. From 5.0.0 to before 5.0.6, the max option was being applied too late. When expanding | May 29, 2026 | 7.5 | 34 | NO | NO |
CVE-2026-14257HIGH brace-expansion through 5.0.7 is vulnerable to denial of service via memory exhaustion. The expand() function limits the number of results with a max option (default 100,000) but d | Jul 23, 2026 | 7.5 | 32 | NO | NO |
CVE-2026-33750HIGH The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13, a brace pattern with a zero step v | Mar 27, 2026 | 7.5 | 31 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Juliangruber.
Media articles that mention a CVE ID that affects a product developed by Juliangruber — matched by CVE ID, not by vendor name.