Network-AI before 5.13.4 contains an improper cryptographic signature verification vulnerability in APSAdapter where the default local verifier accepts any non-empty string as valid. Unauthenticated attackers can submit forged APS delegation payloads with arbitrary scopes to bypass signature verification and obtain signed permission-grant tokens for sensitive resources including SHELL_EXEC.
CVE-2026-64623
Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-20. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 70(Attend)EG Risk 70/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 computedSeverity86% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 10.0%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026Network-AI before 5.13.4 Cryptographic Signature Verification Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/network-ai-before-cryptographic-signature-verification-bypassAPSAdapter Default Local Verifier Accepts Any Non-Empty Signature · Advisory · Jovancoding/Network-AI · GitHub
https://github.com/Jovancoding/Network-AI/security/advisories/GHSA-3jf7-33vc-hgf4Vendor Advisories for CVE-2026-64623(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 15× in last 7d / 15× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 16:40 UTCEG score recompute
- 2026-07-20 16:40 UTCGHSA enrichment
- 2026-07-20 14:56 UTCEG score recompute
- 2026-07-20 14:55 UTCGHSA enrichment
- 2026-07-20 12:37 UTCEG score recompute
- 2026-07-20 12:37 UTCGHSA enrichment
- 2026-07-20 12:18 UTCEG score recompute
- 2026-07-20 12:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-64623?
When was CVE-2026-64623 disclosed?
Is CVE-2026-64623 actively exploited?
What is the CVSS score of CVE-2026-64623?
How do I remediate CVE-2026-64623?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64623
Is Your Infrastructure Affected by CVE-2026-64623?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.