CVE-2026-64622
Received Received - Intake

Network-AI Authorization Bypass Exposes Approval Data

Publication date: 2026-07-20

Last updated on: 2026-07-20

Assigner: VulnCheck

Description
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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-20
Last Modified
2026-07-20
Generated
2026-07-21
AI Q&A
2026-07-20
EPSS Evaluated
N/A
NVD
CVE-2026-64622
EUVD
EUVD-2026-45937

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
network-ai network-ai From 5.12.2 (inc) to 5.13.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-64622 is a missing authorization vulnerability in Network-AI versions 5.12.2 through 5.13.3. It allows unauthenticated actors to access sensitive approval request details via specific GET routes even when a secret is configured. Affected routes include GET /approvals/?status=all, GET /approvals/:id, GET /approvals/stats, and GET /approvals/sse, which expose full ApprovalEntry content such as shell commands, file paths, justifications, and risk levels. All responses also include a hardcoded Access-Control-Allow-Origin: * header, enabling cross-origin data disclosure.

Detection Guidance

Check if your network-ai instance is running versions 5.12.2 through 5.13.3. Test the affected routes by sending GET requests to /approvals/?status=all, /approvals/:id, /approvals/stats, and /approvals/sse. If responses include sensitive data without authentication, the system is vulnerable.

Impact Analysis

This vulnerability allows attackers to retrieve sensitive data such as shell commands, file paths, justifications, and risk levels without authentication. The hardcoded CORS header enables attackers to exfiltrate data from any website the operator visits, potentially leading to unauthorized access, data breaches, or further exploitation of exposed system details.

Compliance Impact

This vulnerability likely violates compliance requirements for GDPR and HIPAA due to unauthorized access to sensitive data. GDPR mandates strict access controls and protection of personal data, while HIPAA requires safeguards for protected health information. Unauthorized disclosure of such data could result in regulatory penalties and legal consequences.

Mitigation Strategies

Upgrade network-ai to a version beyond 5.13.3 where the issue is fixed. Apply authentication checks to all GET routes. Remove the hardcoded Access-Control-Allow-Origin: * header to prevent cross-origin data leaks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64622. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart