CVE-2026-64622

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

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

Network-AI (npm: network-ai) versions 5.12.2 through 5.13.3 fail to apply the configured authorization check (checkAuth/secret) to the ApprovalInbox GET read routes, so even when an operator configures a secret, unauthenticated actors can access sensitive approval request details. The GET /approvals/?status=all, GET /approvals/:id, GET /approvals/stats, and GET /approvals/sse routes disclose full ApprovalEntry content including action/target shell-command strings, file paths, justifications, and risk levels. All responses also carry a hardcoded Access-Control-Allow-Origin: * header, enabling cross-origin disclosure from any website the operator visits. This is an incomplete fix for GHSA-mxjx-28vx-xjjj.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Network-AI 5.12.2 through 5.13.3 Missing Authorization via ApprovalInbox | Advisories | VulnCheck

https://www.vulncheck.com/advisories/network-ai-through-missing-authorization-via-approvalinbox
github Patch Available🟡 PoC Available

** `ApprovalInbox` GET read routes remain unauthenticated and wildcard-CORS after the GHSA-mxjx-28vx-xjjj fix — queued high-risk action content disclosed even when a `secret` is set · Advisory · Jovancoding/Network-AI · GitHub

https://github.com/Jovancoding/Network-AI/security/advisories/GHSA-m4jg-6w3q-gm86

Vendor Advisories for CVE-2026-64622(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 26× in last 7d / 57× 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-08-03 11:55 UTCEG score recompute
  2. 2026-08-03 11:55 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-02 22:53 UTCGHSA enrichment
  5. 2026-08-02 10:39 UTCEG score recompute
  6. 2026-08-02 10:39 UTCGHSA enrichment
  7. 2026-08-02 02:27 UTCEPSS rescore
  8. 2026-08-01 22:24 UTCGHSA enrichment
  9. 2026-08-01 10:09 UTCEG score recompute
  10. 2026-08-01 10:09 UTCGHSA enrichment
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-07-31 21:54 UTCGHSA enrichment
  13. 2026-07-31 09:39 UTCGHSA enrichment
  14. 2026-07-30 21:23 UTCEG score recompute
  15. 2026-07-30 21:23 UTCGHSA enrichment
  16. 2026-07-30 16:28 UTCEPSS rescore
  17. 2026-07-30 08:03 UTCEG score recompute
  18. 2026-07-30 08:03 UTCGHSA enrichment
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-29 18:22 UTCGHSA enrichment
  22. 2026-07-29 06:07 UTCGHSA enrichment
  23. 2026-07-28 17:49 UTCEG score recompute
  24. 2026-07-28 17:49 UTCGHSA enrichment
  25. 2026-07-28 15:37 UTCEPSS rescore
Show 32 more
  1. 2026-07-28 05:32 UTCGHSA enrichment
  2. 2026-07-27 17:16 UTCEG score recompute
  3. 2026-07-27 17:16 UTCGHSA enrichment
  4. 2026-07-27 14:14 UTCEPSS rescore
  5. 2026-07-27 05:00 UTCGHSA enrichment
  6. 2026-07-26 16:45 UTCEG score recompute
  7. 2026-07-26 16:45 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 04:30 UTCEG score recompute
  11. 2026-07-26 04:30 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-24 14:18 UTCEPSS rescore
  16. 2026-07-23 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:22 UTCEG score recompute
  19. 2026-07-22 23:41 UTCEG score recompute
  20. 2026-07-22 23:40 UTCGHSA enrichment
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-21 15:25 UTCEPSS rescore
  25. 2026-07-20 14:57 UTCEG score recompute
  26. 2026-07-20 14:57 UTCGHSA enrichment
  27. 2026-07-20 13:02 UTCEG score recompute
  28. 2026-07-20 13:02 UTCGHSA enrichment
  29. 2026-07-20 12:37 UTCEG score recompute
  30. 2026-07-20 12:37 UTCGHSA enrichment
  31. 2026-07-20 12:18 UTCEG score recompute
  32. 2026-07-20 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64622?
CVE-2026-64622 is a high vulnerability published on July 20, 2026. Network-AI (npm: network-ai) versions 5.12.2 through 5.13.3 fail to apply the configured authorization check (checkAuth/secret) to the ApprovalInbox GET read routes, so even when an operator configures a secret, unauthenticated actors can access sensitive approval request details. The GET…
When was CVE-2026-64622 disclosed?
CVE-2026-64622 was first published in the National Vulnerability Database on July 20, 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-64622 actively exploited?
CVE-2026-64622 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 66.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64622?
CVE-2026-64622 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64622?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64622, 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-64622

Explore →

Is Your Infrastructure Affected by CVE-2026-64622?

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

Start Free Scan →Browse All CVEs