# CVE-2026-58482: Network-AI: ApprovalInbox HTTP server has no authentication — anyone can approve pending agent actions > Unauthenticated HTTP endpoints in Network-AI allow attackers to bypass human-in-the-loop controls and execute high-risk agent actions without consent. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 20 Jul 2026 - **Updated:** 20 Jul 2026 - **Also known as:** GHSA-mxjx-28vx-xjjj ## What is CVE-2026-58482? CVE-2026-58482 is a medium-severity missing authorization vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Network-AI, a TypeScript/Node.js multi-agent orchestrator, has a shipped, exported, documented feature called `ApprovalInbox` (`lib/approval-inbox.ts`). It is the network surface of the human-in-the-loop Approval Gate, which `ApprovalGate` uses to require explicit human approval for high-risk operations. The HTTP server it exposes has no authentication of any kind and sets `Access-Control-Allow-Origin: *` on every route, including the state-changing `POST /approvals/:id/approve` and `/deny`. As a result, in versions 5.0.0 through 5.12.1, any party who can send an HTTP request to the inbox port — a co-located process, a container/SSRF on the same host, a remote client when the operator binds a non-loopback address, or any website the operator visits in a browser (via the wildcard CORS) — can enumerate pending approvals and approve them, defeating the entire human-in-the-loop control and causing the gated high-risk action (e.g. a shell command the agent was holding for review) to execute without consent. This issue is fixed in v5.12.2. `ApprovalInbox` now accepts a `secret` option. When set, the mutating endpoints `POST /:id/approve` and `POST /:id/deny` require an `Authorization: Bearer ` header, validated in constant time with `crypto.timingSafeEqual`. `startServer()` already binds to `127.0.0.1` by default; operators exposing the inbox on a network must set a secret. Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2026-58482? 2 open source packages ship an affected version, including network-ai. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `network-ai` | npm | From 5.0.0 | 5.12.2 | | `network-ai` | npm | From 5.0.0 | 5.12.2 | Products: Network-Ai Network-Ai. ## How do I fix CVE-2026-58482? Upgrade network-ai to 5.12.2 or later. ## Is CVE-2026-58482 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58482 exists. ## Other vulnerabilities in Jovancoding Network-AI - [CVE-2026-46701](https://insights.sbomify.com/CVE-2026-46701/): Network-AI: Unauthenticated Cross-Origin MCP Tool Invocation via Empty Default Secret (high 7.6) - [CVE-2026-58484](https://insights.sbomify.com/CVE-2026-58484/): Network-AI: Poisoned environment backup manifest allows arbitrary recursive deletion during backup pruning (high 7.1) - [CVE-2026-58481](https://insights.sbomify.com/CVE-2026-58481/): Network-AI: AgentRuntime sandbox path-prefix checks allow file access outside the configured base directory (medium 6.5) - [CVE-2026-58413](https://insights.sbomify.com/CVE-2026-58413/): EnvironmentManager.restore() backup ID path traversal copies arbitrary directories into environment data (medium 6.1) - [CVE-2026-58414](https://insights.sbomify.com/CVE-2026-58414/): Network-AI: EnvironmentManager.backup() follows symlinked directories and copies files outside the environment root into backups (medium 5.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-58482 and fix it if it is affected. What it is: CVE-2026-58482 is a medium-severity missing authorization vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58482 exists. Affected packages and fixed versions: - network-ai (npm): affected from 5.0.0; fixed in 5.12.2 - network-ai (npm): affected from 5.0.0; fixed in 5.12.2 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-58482/ (Markdown: https://insights.sbomify.com/CVE-2026-58482/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58482 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58482 - OSV: https://osv.dev/vulnerability/CVE-2026-58482 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-58482/ Summaries are generated and may contain mistakes; the official description above is the record.