CVE-2026-16631

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 vulnerability was detected in publint up to 0.1.4. This impacts the function child_process.exec of the file src/node/pack.js of the component package-manager Command Handler. The manipulation results in os command injection. Attacking locally is a requirement. The exploit is now public and may be used. The patch is identified as adf2d9a09945fc98c85a2520a89f441d78b2dbd8. It is advisable to implement a patch to correct this issue. The project maintainer explains: "I think it's very rare for someone to use this package with untrusted input".

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
47%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jul 26, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
github_pr

Fix command injection in `@publint/pack`

Fix merged in publint/publint PR #238 on 2026-06-17 — awaiting tagged release

https://github.com/publint/publint/pull/238
generic

Command injection in `@publint/pack` via `destination` option · Issue #236 · publint/publint · GitHub

https://github.com/publint/publint/issues/236
github_commit

commit adf2d9a09945 (publint/publint)

Fix landed in publint/publint commit adf2d9a09945 — awaiting tagged release

https://github.com/publint/publint/commit/adf2d9a09945fc98c85a2520a89f441d78b2dbd8
generic

GitHub - publint/publint: Lint packaging errors · GitHub

https://github.com/publint/publint/

Vendor Advisories for CVE-2026-16631(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 22× in last 7d / 22× 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:14 UTCEG score recompute
  2. 2026-07-28 22:14 UTCGHSA enrichment
  3. 2026-07-27 23:42 UTCEG score recompute
  4. 2026-07-27 23:42 UTCGHSA enrichment
  5. 2026-07-27 14:13 UTCEPSS rescore
  6. 2026-07-27 01:31 UTCEG score recompute
  7. 2026-07-27 01:31 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 03:21 UTCEG score recompute
  11. 2026-07-26 03:21 UTCGHSA enrichment
  12. 2026-07-25 14:17 UTCEPSS rescore
  13. 2026-07-25 14:17 UTCEPSS rescore
  14. 2026-07-24 14:17 UTCEPSS rescore
  15. 2026-07-23 16:11 UTCNVD updateCVSS v4 → 1.9
  16. 2026-07-23 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 14:09 UTCMITRE cvelistV5CVSS v4 → 4.8
  19. 2026-07-23 03:06 UTCEG score recompute
  20. 2026-07-23 00:26 UTCNVD updateCVSS v4 → 1.9
  21. 2026-07-22 23:52 UTCEG score recompute
  22. 2026-07-22 23:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16631?
CVE-2026-16631 is a medium vulnerability published on July 22, 2026. A vulnerability was detected in publint up to 0.1.4. This impacts the function child_process.exec of the file src/node/pack.js of the component package-manager Command Handler. The manipulation results in os command injection. Attacking locally is a requirement. The exploit is now public and may be…
When was CVE-2026-16631 disclosed?
CVE-2026-16631 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16631 actively exploited?
CVE-2026-16631 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-16631?
CVE-2026-16631 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-16631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16631, 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-16631

Explore →

Is Your Infrastructure Affected by CVE-2026-16631?

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

Start Free Scan →Browse All CVEs