CVE-2026-30631

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

An issue was discovered in bytebot-ai in commit 3d37894ce07ef8d8b40adc7fd309ad96c2a71313 (2025-09-11) allowing attackers to execute arbitrary code via crafted path to computer_write_file.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 25, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

bytebot RCE description · GitHub

https://gist.github.com/spdc-elm/1a56d53591a929446a54e50e64de9fc0
github_commit

commit 3d37894ce07e (bytebot-ai/bytebot)

Fix landed in bytebot-ai/bytebot commit 3d37894ce07e — awaiting tagged release

https://github.com/bytebot-ai/bytebot/commit/3d37894ce07ef8d8b40adc7fd309ad96c2a71313

Vendor Advisories for CVE-2026-30631(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 43× 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-29 17:11 UTCGHSA enrichment
  2. 2026-07-29 13:09 UTCGHSA enrichment
  3. 2026-07-29 09:08 UTCGHSA enrichment
  4. 2026-07-29 05:08 UTCGHSA enrichment
  5. 2026-07-29 01:05 UTCGHSA enrichment
  6. 2026-07-28 21:04 UTCGHSA enrichment
  7. 2026-07-28 17:03 UTCEG score recompute
  8. 2026-07-28 17:03 UTCGHSA enrichment
  9. 2026-07-28 15:36 UTCEPSS rescore
  10. 2026-07-28 11:41 UTCGHSA enrichment
  11. 2026-07-28 07:37 UTCGHSA enrichment
  12. 2026-07-28 03:35 UTCGHSA enrichment
  13. 2026-07-27 23:34 UTCGHSA enrichment
  14. 2026-07-27 19:15 UTCGHSA enrichment
  15. 2026-07-27 15:13 UTCEG score recompute
  16. 2026-07-27 15:13 UTCGHSA enrichment
  17. 2026-07-27 10:52 UTCGHSA enrichment
  18. 2026-07-27 06:52 UTCGHSA enrichment
  19. 2026-07-27 02:51 UTCGHSA enrichment
  20. 2026-07-26 22:50 UTCGHSA enrichment
  21. 2026-07-26 18:48 UTCEG score recompute
  22. 2026-07-26 18:47 UTCGHSA enrichment
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-26 14:46 UTCGHSA enrichment
Show 18 more
  1. 2026-07-26 10:44 UTCEG score recompute
  2. 2026-07-26 10:44 UTCGHSA enrichment
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-25 14:17 UTCEPSS rescore
  5. 2026-07-24 14:17 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:08 UTCEG score recompute
  9. 2026-07-22 23:25 UTCEG score recompute
  10. 2026-07-22 23:24 UTCGHSA enrichment
  11. 2026-07-22 18:01 UTCEG score recompute▲ 9.80
  12. 2026-07-22 18:01 UTCGHSA enrichment
  13. 2026-07-22 18:00 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 21:19 UTCNVD update
  17. 2026-07-21 20:46 UTCEG score recompute
  18. 2026-07-21 20:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-30631?
CVE-2026-30631 is a critical vulnerability published on July 21, 2026. An issue was discovered in bytebot-ai in commit 3d37894ce07ef8d8b40adc7fd309ad96c2a71313 (2025-09-11) allowing attackers to execute arbitrary code via crafted path to computerwritefile.
When was CVE-2026-30631 disclosed?
CVE-2026-30631 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-30631 actively exploited?
CVE-2026-30631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.2% of all scored CVEs.
What is the CVSS score of CVE-2026-30631?
CVE-2026-30631 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-30631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-30631, 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-30631

Explore →

Is Your Infrastructure Affected by CVE-2026-30631?

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

Start Free Scan →Browse All CVEs