CVE-2026-16735

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-07-23. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jul 26, 2026
No patch confirmed yet.
generic

Command injection via unsanitized `infile` in `git add` · Issue #149 · release-it/conventional-changelog · GitHub

https://github.com/release-it/conventional-changelog/issues/149
generic

GitHub - release-it/conventional-changelog: Conventional changelog plugin for release-it · GitHub

https://github.com/release-it/conventional-changelog/

Vendor Advisories for CVE-2026-16735(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-28 22:13 UTCEG score recompute
  2. 2026-07-28 22:13 UTCGHSA enrichment
  3. 2026-07-27 21:38 UTCEG score recompute
  4. 2026-07-27 21:38 UTCGHSA enrichment
  5. 2026-07-27 21:19 UTCNVD updateCVSS v4 → 1.9
  6. 2026-07-27 20:55 UTCEG score recompute
  7. 2026-07-27 20:55 UTCGHSA enrichment
  8. 2026-07-27 20:54 UTCMITRE cvelistV5CVSS v4 → 4.8
  9. 2026-07-27 14:13 UTCEPSS rescore
  10. 2026-07-27 03:42 UTCEG score recompute
  11. 2026-07-27 03:42 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 03:07 UTCEG score recompute
  15. 2026-07-26 03:07 UTCGHSA enrichment
  16. 2026-07-25 14:17 UTCEPSS rescore
  17. 2026-07-25 14:17 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 16:11 UTCNVD updateCVSS v4 → 1.9
  20. 2026-07-23 14:10 UTCEG score recompute
  21. 2026-07-23 14:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16735?
CVE-2026-16735 is a medium vulnerability published on July 23, 2026. 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…
When was CVE-2026-16735 disclosed?
CVE-2026-16735 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16735 actively exploited?
CVE-2026-16735 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16735?
CVE-2026-16735 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-16735?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16735, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16735

Explore →

Is Your Infrastructure Affected by CVE-2026-16735?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs