CVE-2026-64622
Auth bypass in Network-AI exposes approval entries and secrets via public GET endpoints.
Is CVE-2026-64622 being exploited?
Not confirmed. CVE-2026-64622 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-64622?
CVE-2026-64622 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64622?
Yes. A fix has been recorded for CVE-2026-64622. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64622 affect?
CVE-2026-64622 affects network-ai (npm) 5.12.2-5.13.3, Apps using Network-AI approval endpoints (GET /approvals/*). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64622?
Upgrade to a fixed release if available; enforce auth on approval endpoints and remove CORS wildcard.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated actors can read full approval entries (shell commands, file paths, justifications, risk levels). CORS '*' allows cross-origin exfiltration.
Immediate action required
- affected>= 5.12.2 and <= 5.13.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.