{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107353 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-107353 is a medium-severity code injection vulnerability in ljharb traverse, published on 7 Oct 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-107353 and fix it if it is affected.\n\nWhat it is: CVE-2026-107353 is a medium-severity code injection vulnerability in ljharb traverse, published on 7 Oct 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 CVE-2026-107353 in the wild and no public exploit code.\n\nAffected product: ljharb traverse. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-107353/ (Markdown: https://insights.sbomify.com/CVE-2026-107353/index.md)","id":"CVE-2026-107353","markdown":"https://insights.sbomify.com/CVE-2026-107353/index.md","name":"CVE-2026-107353","record":{"aliases":["AZL-107078","CLSA-2026-1792757149","CLSA-2026-1792757262","CLSA-2026-1792759996","CLSA-2026-1792760030","DEBIAN-CVE-2026-107353","GHSA-rj28-8w7x-jmqc","UBUNTU-CVE-2026-107353"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js traverse library","requires_auth":"none","summary":"Attackers can pollute built-in prototypes via untrusted paths in the traverse library, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"harborist","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"traverse (npm) versions 0.3.6 through 0.3.9, 0.4.0 through 0.4.6, 0.5.0 through 0.5.2, and 0.6.0 through 0.6.11 allow prototype pollution through set(). When the path passed to set() crosses a primitive value, the next path segment is resolved on that primitive's built-in prototype, so an application that passes an untrusted path to set() lets an attacker add or overwrite properties of String.prototype, Number.prototype, or Boolean.prototype using plain JSON data, for example traverse({ name: 'bob' }).set(['name', '__proto__', 'polluted'], 'yes'). Object.prototype was reachable only with a non-data path segment, such as an object whose toString returns a different value on each call, or through a Proxy that accepts an assignment without storing it. This is fixed in 0.3.10, 0.4.7, 0.5.3, and 0.6.12.","ecosystems":[],"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":"traverse: set() can write to built-in prototypes via an untrusted path","id":"CVE-2026-107353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"** This candidate has been removed by an organization.","id":"CVE-2026-107354"},"packages":[],"prev":{"headline":"Missing authorization checks in Amazon Athena engine version 3 request handling","id":"CVE-2026-107352"},"products":["traverse"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["ljharb"]},"summary":"Attackers can pollute built-in prototypes via untrusted paths in the traverse library, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-107353/"}