# CVE-2026-64623: Network-AI before 5.13.4 Cryptographic Signature Verification Bypass

> Attackers can bypass signature verification to obtain signed tokens for sensitive resources, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-37v5-gpcx-w9fc, GHSA-3jf7-33vc-hgf4

## What is CVE-2026-64623?

CVE-2026-64623 is a high-severity vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-64623?


## How do I fix CVE-2026-64623?

No fix has been published for CVE-2026-64623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64623 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64623 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64623 and fix it if it is affected.

What it is: CVE-2026-64623 is a high-severity vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64623 exists.

Affected product: Jovancoding Network-AI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64623/ (Markdown: https://insights.sbomify.com/CVE-2026-64623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64623
- OSV: https://osv.dev/vulnerability/CVE-2026-64623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64623/
Summaries are generated and may contain mistakes; the official description above is the record.