{"answers":{"affected":"2 open source packages ship an affected version, including smol-toml.","exploited":"There is no known exploitation of GHSA-v3rj-xjv7-4jmq in the wild and no public exploit code.","fix":"Upgrade smol-toml to 1.6.1 or later.","what":"GHSA-v3rj-xjv7-4jmq is a denial of service vulnerability in smol-toml, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-v3rj-xjv7-4jmq and fix it if it is affected.\n\nWhat it is: GHSA-v3rj-xjv7-4jmq is a denial of service vulnerability in smol-toml, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-v3rj-xjv7-4jmq in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smol-toml (npm): affected all versions; fixed in 1.6.1\n- smol-toml (npm): affected all versions; fixed in 1.6.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/GHSA-v3rj-xjv7-4jmq/ (Markdown: https://insights.sbomify.com/GHSA-v3rj-xjv7-4jmq/index.md)","id":"GHSA-v3rj-xjv7-4jmq","markdown":"https://insights.sbomify.com/GHSA-v3rj-xjv7-4jmq/index.md","name":"GHSA-v3rj-xjv7-4jmq","record":{"aliases":[],"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":"An attacker can crash applications parsing untrusted TOML by sending documents with thousands of consecutive comments, causing a stack overflow.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nAn attacker can send a maliciously crafted TOML to cause the parser to crash, because of a stack overflow caused by thousands of consecutive commented lines.\n\nThe library uses recursion internally while parsing to skip over commented lines, which can be exploited to crash an application that is processing arbitrary TOML documents.\n\n### Proof of concept\n```js\nrequire(\"smol-toml\").parse('# comment\\n'.repeat(8000) + 'key = \"value\"')\n```\n\n### Impact\nApplications which parse arbitrary TOML documents may suffer availability issues if they receive malicious input. If uncaught, the crash may cause the application itself to crash. The impact is deemed minor, as the function is already likely to throw errors on invalid input. Downstream users are supposed to properly handle errors in such situations.\n\nDue to the design of most JavaScript runtimes, the uncontrolled recursion does not lead to excessive memory usage and the execution is quickly aborted.\n\nAs a reminder, it is **strongly** advised when working with untrusted user input to expect errors to occur and to appropriately catch them.\n\n### Patches\nVersion 1.6.1 uses a different approach for parsing comments, which no longer involves recursion.\n\n### Workarounds\nWrap all invocations of `parse` and `stringify` in a try/catch block when dealing with untrusted user input.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"smol-toml: Denial of Service via TOML documents containing thousands of consecutive commented lines","id":"GHSA-v3rj-xjv7-4jmq","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["1.6.1"],"introduced":["0"],"last_affected":[],"package":"smol-toml","purl":null,"source":"GHSA-v3rj-xjv7-4jmq"},{"ecosystem":"npm","fixed":["1.6.1"],"introduced":["0"],"last_affected":[],"package":"smol-toml","purl":"pkg:npm/smol-toml","source":"GHSA-v3rj-xjv7-4jmq"}],"products":null,"published":"2026-03-25","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can crash applications parsing untrusted TOML by sending documents with thousands of consecutive comments, causing a stack overflow.","url":"https://insights.sbomify.com/GHSA-v3rj-xjv7-4jmq/"}