dynoxide-rs
Affected
- introduced
0.9.3, fixed0.9.13(semver)
Fixed versions
0.9.13
Fix
- Fixed version
0.9.13cargo update -p dynoxide-rs --precise 0.9.13
Advisory
Also known as: CVE-2026-42559, GHSA-89vp-x53w-74fx, GHSA-fvh2-gm75-j4j7, RUSTSEC-2026-0189
DNS rebinding and cross-origin CSRF in dynoxide's MCP HTTP transport
dynoxide's MCP HTTP transport was vulnerable to DNS rebinding via its transitive rmcp dependency, plus a related cross-origin CSRF gap.
A malicious web page could make the user's browser send requests to a local dynoxide mcp --http or dynoxide serve --mcp server with a non-loopback Host header, which the server would then process. The Host check alone did not close a related cross-origin CSRF vector: a page could fetch the loopback endpoint with mode: 'no-cors', and the Host header would match while the Origin header went unchecked.
Affected MCP write tools include put_item, update_item, delete_item, create_table, and batch_write_item.
The stdio transport (dynoxide mcp without --http) is not affected.
Patches
dynoxide 0.9.13 closes both vectors:
rmcp from 1.1.1 to 1.6.0 (which ships a default Host-header allowlist).allowed_hosts and allowed_origins on StreamableHttpServerConfig.High Basis: CVSS v3 score 8.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
0.9.3, fixed 0.9.13 (semver)0.9.13
0.9.13cargo update -p dynoxide-rs --precise 0.9.13Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0