CVE-2026-58482 Network-AI vulnerability
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 <secret>` 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.
Browse Node.js security risksQuick answer
Jovancoding Network-AI should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- >= 5.0.0, < 5.12.2
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-58482 affects Network-AI and involves cross-site request forgery. An attacker may cause a signed-in user's browser to perform an unintended state-changing action. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade Network-AI to 5.12.2 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Network-AI.
- Compare the installed version with the recorded affected range: >= 5.0.0, < 5.12.2.
- Upgrade Network-AI to 5.12.2 or a later vendor-supported fixed release.
- Until patched, block state-changing GET routes and require same-origin requests plus a validated anti-CSRF token for every mutation.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Network-AI; remove access that is not required.
- Review web, audit, and object-change logs for state changes initiated through unexpected GET requests, origins, or referrers.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-58482 in place.
- Use a safe regression test to confirm the affected cross-site request forgery path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-58482?
Jovancoding Network-AI versions listed as affected should be reviewed: >= 5.0.0, < 5.12.2.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.