CVE-2026-64622: Network-AI 5.12.2 through 5.13.3 Missing Authorization via ApprovalInbox
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.
Security readout for executives and security teams
Plain-English summary
Network-AI may expose sensitive approval records to anyone who can reach its ApprovalInbox service, even when the operator configured a secret. Any website visited by an operator may also be able to read this data because responses permit all origins. Exposed records can reveal intended actions, command strings, file paths, justifications, and risk assessments.
Executive priority
Treat internet-accessible or broadly reachable deployments as an immediate remediation priority. Sensitive operational details may be exposed despite configured authentication, creating follow-on compromise risk. Isolate affected interfaces, investigate access, and obtain vendor-confirmed remediation. Internal-only deployments still require prompt review because any reachable unauthenticated user may access approval data.
Technical view
Network-AI 5.12.2 through 5.13.3 reportedly omits checkAuth/secret enforcement on four ApprovalInbox GET routes. The routes return full ApprovalEntry content and use Access-Control-Allow-Origin: *. This is classified as CWE-862 and described as an incomplete fix for GHSA-mxjx-28vx-xjjj. The supplied CVSS 4.0 score is 9.3.
Likely exposure
Exposure is likely where an affected ApprovalInbox endpoint is reachable by untrusted networks or users. Configuring checkAuth/secret alone does not protect the identified read routes. Permissive cross-origin responses increase exposure when an operator visits an untrusted website. The bundle’s structured affected data is incomplete, so confirm deployed versions carefully.
Exploitation context
The source bundle does not identify public exploitation, and the CVE is not listed as KEV. Exploitation would reportedly require network access to the affected ApprovalInbox routes but no privileges or user interaction. The permissive cross-origin policy creates an additional browser-based disclosure path; no observed exploitation evidence is provided.
Researcher notes
Affected routes are GET /approvals/?status=all, /approvals/:id, /approvals/stats, and /approvals/sse. Reported disclosure includes complete ApprovalEntry data. The supplied affected-version structure lists only 5.12.2 while the title and description specify 5.12.2 through 5.13.3. No fixed version, patch details, proof of exploitation, or KEV evidence is supplied.
Mitigation direction
Inventory Network-AI deployments and identify versions 5.12.2 through 5.13.3.
Restrict ApprovalInbox access to trusted networks and authenticated intermediaries.
Check the vendor advisory for an approved fixed version or mitigation.
Review exposed approval records and rotate any credentials or secrets they contained.
Investigate historical access to the affected routes for unauthorized disclosure.
Validation and detection
Confirm the deployed Network-AI version and ApprovalInbox network exposure.
Verify every identified GET route rejects unauthenticated requests.
Confirm responses no longer permit arbitrary cross-origin access.
Review relevant request logs for unexpected clients, origins, or access patterns.
Validate remediation against current vendor guidance before restoring broader access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.