{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16735 exists.","fix":"No fix has been published for CVE-2026-16735 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-16735 is a medium-severity command injection vulnerability in release-it conventional-changelog, published on 23 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-16735 and fix it if it is affected.\n\nWhat it is: CVE-2026-16735 is a medium-severity command injection vulnerability in release-it conventional-changelog, published on 23 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16735 exists.\n\nAffected product: release-it conventional-changelog. 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-16735/ (Markdown: https://insights.sbomify.com/CVE-2026-16735/index.md)","id":"CVE-2026-16735","markdown":"https://insights.sbomify.com/CVE-2026-16735/index.md","name":"CVE-2026-16735","record":{"aliases":["GHSA-wmpm-jc79-f6jv"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"release-it conventional-changelog","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary OS commands via the writeChangelog function in release-it conventional-changelog due to improper input handling.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"A security vulnerability has been detected in release-it conventional-changelog up to 11.0.1. This affects the function writeChangelog of the file index.js of the component Changelog File Handler. Such manipulation of the argument infile leads to os command injection. The attack must be carried out locally. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"release-it conventional-changelog Changelog File index.js writeChangelog os command injection","id":"CVE-2026-16735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"User Registration \u0026 Membership \u003c 5.2.6 - Unauthenticated Account Creation While Registration Disabled","id":"CVE-2026-16736"},"packages":[],"prev":{"headline":"Stripe Payment Forms by WP Full Pay \u003c 8.5.2 - Unauthenticated Payment Intent Amount Manipulation","id":"CVE-2026-16734"},"products":["conventional-changelog"],"published":"2026-07-23","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-27","vendors":["release-it"]},"summary":"Local attackers can execute arbitrary OS commands via the writeChangelog function in release-it conventional-changelog due to improper input handling.","url":"https://insights.sbomify.com/CVE-2026-16735/"}