{"answers":{"affected":"2 open source packages ship an affected version, including js-toml. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49293 exists.","fix":"Upgrade js-toml to 1.1.1 or later.","what":"CVE-2026-49293 is a high-severity denial of service vulnerability in sunnyadn js-toml, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49293 and fix it if it is affected.\n\nWhat it is: CVE-2026-49293 is a high-severity denial of service vulnerability in sunnyadn js-toml, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49293 exists.\n\nAffected packages and fixed versions:\n- js-toml (npm): affected all versions; fixed in 1.1.1\n- js-toml (npm): affected all versions; fixed in 1.1.1\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-49293/ (Markdown: https://insights.sbomify.com/CVE-2026-49293/index.md)","id":"CVE-2026-49293","markdown":"https://insights.sbomify.com/CVE-2026-49293/index.md","name":"CVE-2026-49293","record":{"aliases":["GHSA-wp3c-266w-4qfq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript TOML parser","requires_auth":"none","summary":"Attackers can cause CPU exhaustion and denial of service by submitting TOML documents with excessively long integer literals to applications using the js-toml library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"js-toml","vendor":"sunnyadn"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. Versions up to and including 1.1.0 parse hexadecimal / octal / binary integer literals via a hand-written `parseBigInt` loop that multiplies a `BigInt` accumulator by the radix once per input digit. Each iteration performs a `BigInt * BigInt` operation on an accumulator that grows linearly with the number of digits already consumed, so the whole loop is O(n²) in the literal length. The lexer regex places no upper bound on the literal length, so a single TOML document containing one ~500 kB hex literal pins one CPU core for ~40 seconds on a modern laptop (Apple M-series, Node v22). Memory amplification is bounded but CPU amplification is severe and grows quadratically: doubling the literal length quadruples the work. A caller that invokes `load()` on attacker-controlled TOML (configuration upload endpoints, CI/CD systems ingesting third-party `*.toml`, IDE plugins, build tools) is exposed to a single-request CPU exhaustion DoS. Version 1.1.1 fixes the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals","id":"CVE-2026-49293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Valhalla has reflected XSS via unsanitized JSONP callback parameter","id":"CVE-2026-49294"},"packages":[{"ecosystem":"npm","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"js-toml","purl":null,"source":"GHSA-wp3c-266w-4qfq"},{"ecosystem":"npm","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"js-toml","purl":"pkg:npm/js-toml","source":"GHSA-wp3c-266w-4qfq"}],"prev":{"headline":"Kiwi TCMS: The /init-db/ page renders and responds to requests after first use","id":"CVE-2026-49292"},"products":["js-toml"],"published":"2026-06-19","related":[{"cvss_score":7.9,"headline":"js-toml is vulnerable to Prototype Pollution","id":"CVE-2025-54803","kev_date_added":null,"published":"2025-08-05"}],"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":"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["sunnyadn"]},"summary":"Attackers can cause CPU exhaustion and denial of service by submitting TOML documents with excessively long integer literals to applications using the js-toml library.","url":"https://insights.sbomify.com/CVE-2026-49293/"}