{"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-2025-54803 exists.","fix":"Upgrade js-toml to 1.0.2 or later.","what":"CVE-2025-54803 is a high-severity vulnerability in sunnyadn js-toml, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54803 and fix it if it is affected.\n\nWhat it is: CVE-2025-54803 is a high-severity vulnerability in sunnyadn js-toml, published on 5 Aug 2025. 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-2025-54803 exists.\n\nAffected packages and fixed versions:\n- js-toml (npm): affected all versions; fixed in 1.0.2\n- js-toml (npm): affected all versions; fixed in 1.0.2\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-2025-54803/ (Markdown: https://insights.sbomify.com/CVE-2025-54803/index.md)","id":"CVE-2025-54803","markdown":"https://insights.sbomify.com/CVE-2025-54803/index.md","name":"CVE-2025-54803","record":{"aliases":["GHSA-65fc-cr5f-v7r2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript TOML parser","requires_auth":"none","summary":"A remote attacker can pollute the global Object prototype via malicious TOML input, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"js-toml","vendor":"sunnyadn"}],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. In versions below 1.0.2, a prototype pollution vulnerability in js-toml allows a remote attacker to add or modify properties of the global Object.prototype by parsing a maliciously crafted TOML input. This is fixed in version 1.0.2.","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":"js-toml is vulnerable to Prototype Pollution","id":"CVE-2025-54803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Russh is missing an overflow check during channel windows adjust","id":"CVE-2025-54804"},"packages":[{"ecosystem":"npm","fixed":["1.0.2"],"introduced":["0"],"last_affected":[],"package":"js-toml","purl":null,"source":"GHSA-65fc-cr5f-v7r2"},{"ecosystem":"npm","fixed":["1.0.2"],"introduced":["0"],"last_affected":[],"package":"js-toml","purl":"pkg:npm/js-toml","source":"GHSA-65fc-cr5f-v7r2"}],"prev":{"headline":"pyLoad CNL Blueprint is vulnerable to Path Traversal through `dlc_path` leading to Remote Code Execution (RCE)","id":"CVE-2025-54802"},"products":["js-toml"],"published":"2025-08-05","related":[{"cvss_score":7.5,"headline":"CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals","id":"CVE-2026-49293","kev_date_added":null,"published":"2026-06-19"}],"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":"2025-08-05","vendors":["sunnyadn"]},"summary":"A remote attacker can pollute the global Object prototype via malicious TOML input, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-54803/"}