Quick answers
- Is CVE-2026-64623 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64623 being exploited in the wild.
- How severe is CVE-2026-64623?
- High severity, with a CVSS score of 8.6, published 20 July 2026.
- Which products and versions are affected?
- Jovancoding Network-AI < 5.13.4.
- Is there a fix for CVE-2026-64623?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-64623 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-64623?
- Check whether you run Jovancoding Network-AI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An improper cryptographic signature verification vulnerability (CWE-347) exists in the APSAdapter component of Network-AI. By default, the 'local' verification mode uses a fallback verifier that considers any non-empty string to be a valid signature. An unauthenticated remote attacker can exploit this by submitting a forged APS delegation payload with a single-character signature and arbitrary scopes (such as 'shell:exec'). This allows the attacker to bypass signature checks, register forged trust configurations in AuthGuardian, and obtain signed permission-grant tokens for sensitive resources. The issue is fixed in version 5.13.4 by requiring a valid signature function when using local verification mode.
Affected products
- Jovancoding Network-AI < 5.13.4
Timeline
- 2026-07-05: advisory: GitHub Security Advisory GHSA-3jf7-33vc-hgf4 published
- 2026-07-20: disclosed: NVD publication date