{"answers":{"affected":"2 open source packages ship an affected version, including brace-expansion. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45149 in the wild and no public exploit code.","fix":"Upgrade brace-expansion to 5.0.6 or later.","what":"CVE-2026-45149 is a medium-severity denial of service vulnerability in juliangruber brace-expansion, published on 29 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-45149 and fix it if it is affected.\n\nWhat it is: CVE-2026-45149 is a medium-severity denial of service vulnerability in juliangruber brace-expansion, published on 29 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-45149 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- brace-expansion (npm): affected from 5.0.0; fixed in 5.0.6\n- brace-expansion (npm): affected from 5.0.0; fixed in 5.0.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45149/ (Markdown: https://insights.sbomify.com/CVE-2026-45149/index.md)","id":"CVE-2026-45149","markdown":"https://insights.sbomify.com/CVE-2026-45149/index.md","name":"CVE-2026-45149","record":{"aliases":["CLEANSTART-2026-EQ50316","CLEANSTART-2026-GE92046","CLEANSTART-2026-HT65704","CLEANSTART-2026-ZT84089","CLSA-2026-1791215768","CLSA-2026-1791226577","DEBIAN-CVE-2026-45149","ECHO-b5c0-4020-9633","GHSA-jxxr-4gwj-5jf2","MINI-5r6j-f2m5-pg5v","MINI-682j-hr9p-pp7p","MINI-97px-33gj-7h87","MINI-cj2c-q547-3m6v","MINI-cp3w-q34f-8mpm","MINI-fwq6-3xjv-47f9","MINI-hqx4-qpv3-xp9h","MINI-p9qf-rf93-g6w7","MINI-q6x9-2qp2-xjqc","MINI-vmr3-6pqh-wrw4","MINI-wg87-g3jg-gh3x","RHSA-2026:13874","ROOT-APP-NPM-CVE-2026-45149","UBUNTU-CVE-2026-45149"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript brace expansion library","requires_auth":"none","summary":"Attackers can cause excessive memory and CPU consumption in the brace-expansion library by triggering large numeric range expansions before the limit is applied.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"brace-expansion","vendor":"juliangruber"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"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 a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate elements before the max limit is applied With max=10, the output is correctly limited to 10 items, but the process still allocates ~505 MB and spends ~800ms building the full intermediate array. This vulnerability is fixed in 5.0.6.","ecosystems":["Red Hat:hummingbird:1","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"brace-expansion: Large numeric range defeats documented `max` DoS protection","id":"CVE-2026-45149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":10,"n_references":1,"next":{"headline":"Zen Browser - Missing Fullscreen Security Notification Allows Origin Spoofing","id":"CVE-2026-45150"},"packages":[{"ecosystem":"npm","fixed":["5.0.6"],"introduced":["5.0.0"],"last_affected":[],"package":"brace-expansion","purl":null,"source":"GHSA-jxxr-4gwj-5jf2"},{"ecosystem":"npm","fixed":["5.0.6"],"introduced":["5.0.0"],"last_affected":[],"package":"brace-expansion","purl":"pkg:npm/brace-expansion","source":"GHSA-jxxr-4gwj-5jf2"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24","purl":"pkg:rpm/redhat/nodejs24","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-bin","purl":"pkg:rpm/redhat/nodejs24-bin","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-devel","purl":"pkg:rpm/redhat/nodejs24-devel","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-docs","purl":"pkg:rpm/redhat/nodejs24-docs","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-full-i18n","purl":"pkg:rpm/redhat/nodejs24-full-i18n","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-libs","purl":"pkg:rpm/redhat/nodejs24-libs","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:11.12.1-1.24.15.0.1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-npm","purl":"pkg:rpm/redhat/nodejs24-npm","source":"RHSA-2026:13874"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.15.0-1.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-npm-bin","purl":"pkg:rpm/redhat/nodejs24-npm-bin","source":"RHSA-2026:13874"}],"prev":{"headline":"SiYuan: Broken access control in SiYuan publish-mode Readers can enumerate metadata","id":"CVE-2026-45148"},"products":["brace-expansion"],"published":"2026-05-29","related":[{"cvss_score":7.5,"headline":"brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation","id":"CVE-2026-69152","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":7.5,"headline":"brace-expansion DoS via unbounded expansion length causing an out-of-memory process crash","id":"CVE-2026-14257","kev_date_added":null,"published":"2026-07-23"},{"cvss_score":6.5,"headline":"brace-expansion: Zero-step sequence causes process hang and memory exhaustion","id":"CVE-2026-33750","kev_date_added":null,"published":"2026-03-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["juliangruber"]},"summary":"Attackers can cause excessive memory and CPU consumption in the brace-expansion library by triggering large numeric range expansions before the limit is applied.","url":"https://insights.sbomify.com/CVE-2026-45149/"}