Vulnerabilities in pkg:npm/dynoxide

PACKAGE
Advisory Summary

GHSA-fvh2-gm75-j4j7 is a HIGH (CVSS 7.5) dns rebinding and cross-origin csrf vulnerability (CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action) affecting dynoxide libraries in the crates.io ecosystem. The issue involves dns rebinding and cross-origin csrf via mcp http transport. Remediation is available by upgrading affected packages to version 0.9.13.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/dynoxide

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/dynoxide. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fvh2-gm75-j4j7 - HIGH dynoxide: DNS rebinding and cross-origin CSRF via MCP HTTP transport

GHSA-fvh2-gm75-j4j7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-fvh2-gm75-j4j7
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action
Affected Product dynoxide
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-fvh2-gm75-j4j7

To remediate this vulnerability, upgrade all affected dynoxide dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

dynoxide-rs fixed: 0.9.13
Upgrade dynoxide-rs to 0.9.13
dynoxide fixed: 0.9.13
npm install dynoxide@0.9.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for dynoxide-rs

How to Check if You Are Affected

To determine whether your application is affected by GHSA-fvh2-gm75-j4j7, inspect your project dependencies for dynoxide:

inspect dependencies for dynoxide-rs

Analyze the terminal output to locate any version of dynoxide in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.9.13), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action, where the product performs reverse dns resolution on an ip address to obtain the hostname and make a security decision, but it does not properly ensure that the ip address is truly associated with the hostname. In dynoxide, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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. Affects 0.9.3 to 0.9.12. The stdio transport (`dynoxide mcp` without `--http`, which is the default) is not affected. ## Impact If a user is running `dynoxide mcp --http` (or `dynoxide serve --mcp`) on their machine and then visits a malicious web page, the attacker's JavaScript can call any MCP tool exposed by the running dynoxide instance. Reachable tools include reads (`get_item`, `query`, `scan`, `batch_get_item`, `describe_table`, `list_tables`) and writes (`put_item`, `update_item`, `delete_item`, `create_table`, `batch_write_item`). Any data in tables that the local dynoxide instance has access to can be read, modified, or destroyed. ## Patches dynoxide 0.9.13 closes both the named CVE and a related cross-origin CSRF gap: 1. **DNS rebinding (the named CVE).** `rmcp` is upgraded from 1.1.1 to 1.6.0. rmcp 1.4+ ships a default Host-header allowlist (`["localhost", "127.0.0.1", "::1"]`) which rejects requests carrying any other Host header with a 403. 2. **Defence in depth.** Explicit `allowed_hosts` and `allowed_origins` lists are now set on `StreamableHttpServerConfig` directly. The Host allowlist protects against a future rmcp default flip. The Origin allowlist closes a related cross-origin CSRF gap that the Host check alone does not address: a malicious page could `fetch` the loopback endpoint with `mode: 'no-cors'`, the Host header would match (it's the literal loopback address the browser is connecting to), but the Origin header would otherwise have been unchecked. Native MCP clients that don't send an Origin header (Claude Code, Cursor, the dynoxide CLI) are unaffected by the Origin check and continue to work. ## Workarounds - Upgrade to dynoxide 0.9.13. - If upgrade is not immediately possible: do not run the MCP HTTP transport. Run `dynoxide mcp` (stdio, the default) instead of `dynoxide mcp --http`, and don't pass `--mcp` to `dynoxide serve`. ## Resources - Upstream rmcp advisory: [GHSA-89vp-x53w-74fx](https://github.com/modelcontextprotocol/rust-sdk/security/advisories/GHSA-89vp-x53w-74fx) - Upstream CVE: [CVE-2026-42559](https://www.cve.org/CVERecord?id=CVE-2026-42559) - dynoxide release: [v0.9.13](https://github.com/nubo-db/dynoxide/releases/tag/v0.9.13) - MCP transport security guidance: <https://modelcontextprotocol.io/specification/2025-11-25/basic/transports#security-warning> ## Credits Vulnerability identified via GitHub Dependabot alert on the transitive rmcp dependency.

GHSA-fvh2-gm75-j4j7 Affected dynoxide Versions

2 component(s)
Fixed Versions:
0.9.13
Product / Package Ecosystem Affected Versions Fixed Version
dynoxide-rs
crates.io
≥ 0.9.3
< 0.9.13
0.9.13
dynoxide
npm
≥ 0.9.3
< 0.9.13
0.9.13

References

Frequently Asked Questions

What is GHSA-fvh2-gm75-j4j7?
GHSA-fvh2-gm75-j4j7 is a security vulnerability in dynoxide involving DNS rebinding and cross-origin CSRF via MCP HTTP transport under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action.
Which dynoxide versions are affected?
Affected versions include releases prior to 0.9.13 across affected packages: dynoxide-rs, dynoxide.
What version fixes GHSA-fvh2-gm75-j4j7?
Upgrading to 0.9.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is dynoxide-rs affected?
Yes, dynoxide-rs is affected in releases prior to 0.9.13. Upgrade your dependency to 0.9.13 or later.
Is dynoxide affected?
Yes, dynoxide is affected in releases prior to 0.9.13. Upgrade your dependency to 0.9.13 or later.
What is the CVSS score of GHSA-fvh2-gm75-j4j7?
GHSA-fvh2-gm75-j4j7 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-fvh2-gm75-j4j7?
GHSA-fvh2-gm75-j4j7 is classified under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action (The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.).
How can I check crates.io dependencies for GHSA-fvh2-gm75-j4j7?
Run the dependency tree command: 'inspect dependencies for dynoxide-rs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fvh2-gm75-j4j7",
  "modified" : "2026-05-18T17:00:25Z",
  "published" : "2026-05-18T17:00:25Z",
  "aliases" : [ ],
  "summary" : "dynoxide: DNS rebinding and cross-origin CSRF via MCP HTTP transport",
  "details" : "## Summary\n\ndynoxide'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. Affects 0.9.3 to 0.9.12. The stdio transport (`dynoxide mcp` without `--http`, which is the default) is not affected.\n\n## Impact\n\nIf a user is running `dynoxide mcp --http` (or `dynoxide serve --mcp`) on their machine and then visits a malicious web page, the attacker's JavaScript can call any MCP tool exposed by the running dynoxide instance.\n\nReachable tools include reads (`get_item`, `query`, `scan`, `batch_get_item`, `describe_table`, `list_tables`) and writes (`put_item`, `update_item`, `delete_item`, `create_table`, `batch_write_item`).\n\nAny data in tables that the local dynoxide instance has access to can be read, modified, or destroyed.\n\n## Patches\n\ndynoxide 0.9.13 closes both the named CVE and a related cross-origin CSRF gap:\n\n1. **DNS rebinding (the named CVE).** `rmcp` is upgraded from 1.1.1 to 1.6.0. rmcp 1.4+ ships a default Host-header allowlist (`[\"localhost\", \"127.0.0.1\", \"::1\"]`) which rejects requests carrying any other Host header with a 403.\n\n2. **Defence in depth.** Explicit `allowed_hosts` and `allowed_origins` lists are now set on `StreamableHttpServerConfig` directly. The Host allowlist protects against a future rmcp default flip. The Origin allowlist closes a related cross-origin CSRF gap that the Host check alone does not address: a malicious page could `fetch` the loopback endpoint with `mode: 'no-cors'`, the Host header would match (it's the literal loopback address the browser is connecting to), but the Origin header would otherwise have been unchecked.\n\nNative MCP clients that don't send an Origin header (Claude Code, Cursor, the dynoxide CLI) are unaffected by the Origin check and continue to work.\n\n## Workarounds\n\n- Upgrade to dynoxide 0.9.13.\n- If upgrade is not immediately possible: do not run the MCP HTTP transport. Run `dynoxide mcp` (stdio, the default) instead of `dynoxide mcp --http`, and don't pass `--mcp` to `dynoxide serve`.\n\n## Resources\n\n- Upstream rmcp advisory: [GHSA-89vp-x53w-74fx](https://github.com/modelcontextprotocol/rust-sdk/security/advisories/GHSA-89vp-x53w-74fx)\n- Upstream CVE: [CVE-2026-42559](https://www.cve.org/CVERecord?id=CVE-2026-42559)\n- dynoxide release: [v0.9.13](https://github.com/nubo-db/dynoxide/releases/tag/v0.9.13)\n- MCP transport security guidance: <https://modelcontextprotocol.io/specification/2025-11-25/basic/transports#security-warning>\n\n## Credits\n\nVulnerability identified via GitHub Dependabot alert on the transitive rmcp dependency.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "dynoxide-rs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.3"
      }, {
        "fixed" : "0.9.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "dynoxide"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.3"
      }, {
        "fixed" : "0.9.13"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nubo-db/dynoxide/security/advisories/GHSA-fvh2-gm75-j4j7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nubo-db/dynoxide"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nubo-db/dynoxide/releases/tag/v0.9.13"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0140.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-346", "CWE-350", "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-18T17:00:25Z",
    "nvd_published_at" : null
  }
}