Quick answers
- Is CVE-2026-42856 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42856 being exploited in the wild.
- How severe is CVE-2026-42856?
- High severity, with a CVSS score of 4, published 11 May 2026.
- Which products and versions are affected?
- Jovancoding Network-AI <= 5.1.2; network-ai (npm) SEMVER:introduced=0,fixed=5.1.3.
- Is there a fix for CVE-2026-42856?
- Yes. network-ai (npm): upgrade to 5.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42856 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42856?
- Check whether you run Jovancoding Network-AI or network-ai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- network-ai (npm): upgrade to 5.1.3 or later
npm install network-ai@5.1.3
Technical details
The Model Context Protocol (MCP) HTTP transport in Network-AI fails to implement authentication, session, or token checks in its `_handlePost()` and `handleRPC()` functions. By default, the server binds to `0.0.0.0`, making it reachable over the network. An unauthenticated attacker can send JSON-RPC `tools/call` requests to invoke privileged tools such as `config_set`, `agent_spawn`, and `token_create`. This allows for full enumeration and mutation of the orchestrator's live configuration, agent management, and security token lifecycle. The vulnerability is addressed in version 5.1.3.
Affected products
- Jovancoding Network-AI <= 5.1.2
Identifiers
- CVE-2026-42856
- GHSA-fj4g-2p96-q6m3
Timeline
- 2026-04-21: other: Reporter validation date
- 2026-04-24: advisory: GitHub Advisory published
- 2026-05-05: disclosed: CVE-2026-42856 assigned