CVE-2026-45310: Deepseek tui DeepSeek TUI Has SSRF Vulnerability

HIGH
Advisory Identifier: GHSA-96ff-gc8g-wpvg
CVSS 7.4
CWE-918
Published
Advisory Summary

CVE-2026-45310 is a HIGH (CVSS 7.4) deepseek tui has ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Deepseek tui libraries in the crates.io ecosystem. The issue involves deepseek tui has ssrf via http redirect bypass in fetch_url tool. Remediation is available by upgrading affected packages to version 0.8.22.

CVE-2026-45310 at a Glance

CVE Identifier CVE-2026-45310
GHSA Identifier GHSA-96ff-gc8g-wpvg
Severity HIGH
CVSS v3.1 Base Score 7.4
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Deepseek tui
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.4

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

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

How to Fix CVE-2026-45310

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

deepseek-tui fixed: 0.8.22
Upgrade deepseek-tui to 0.8.22
deepseek-tui-cli fixed: 0.8.22
Upgrade deepseek-tui-cli to 0.8.22
deepseek-tui fixed: 0.8.22
npm install deepseek-tui@0.8.22
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 deepseek-tui

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-45310, inspect your project dependencies for Deepseek tui:

inspect dependencies for deepseek-tui

Analyze the terminal output to locate any version of Deepseek tui in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.22), 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Deepseek tui, 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 The `fetch_url` tool validates the initial URL's resolved IP address against a restricted-IP blocklist (`is_restricted_ip()`) to prevent SSRF attacks against internal services (cloud metadata endpoints, localhost, private networks). However, the HTTP client (`reqwest`) is configured to automatically follow up to 5 redirects (`reqwest::redirect::Policy::limited(5)`) without re-validating the redirect target against the same SSRF protections. ### PoC **Step 1 — Baseline:** Confirm `fetch_url` blocks direct requests to restricted IPs. ``` Prompt: use fetch_url to fetch http://169.254.169.254/latest/meta-data/ Expected: Error — "restricted address (private/loopback/link-local)" ``` **Step 2 — SSRF bypass via redirect:** Fetch a public URL that redirects to the restricted IP. ``` Prompt: use fetch_url to fetch http://httpbin.org/redirect-to?url=http://169.254.169.254/latest/meta-data/&status_code=302 ``` **Expected result:** The error message says "connection refused" or "request failed: connect error" — NOT "restricted address." This proves the SSRF filter was bypassed; the connection failed only because `169.254.169.254` is unreachable from a non-cloud machine. **Observed result:** `fetch_url` followed the 302 redirect and attempted to connect to `169.254.169.254`. The error was a TCP-level connection failure, confirming the application-layer SSRF check was not applied to the redirect target. **Step 3 — Redirect to attacker-controlled host:** Confirm attacker-controlled redirect targets are followed. ``` Prompt: use fetch_url to fetch http://httpbin.org/redirect-to?url=http://[collaborator-domain]/ssrf-redirect-bypass&status_code=302 Expected: Collaborator receives HTTP callback at /ssrf-redirect-bypass, confirming the redirect was followed. ``` ### Impact On cloud-hosted instances (AWS, GCP, Azure), an attacker can exfiltrate cloud IAM credentials, instance metadata, and other sensitive internal service data by redirecting `fetch_url` to `http://169.254.169.254/latest/meta-data/`. The attack is triggered via prompt injection (malicious instructions embedded in files or web content the model processes) that cause the model to call `fetch_url` with an attacker-controlled URL.

CVE-2026-45310 Affected Deepseek tui Versions

3 component(s)
Fixed Versions:
0.8.22
Product / Package Ecosystem Affected Versions Fixed Version
deepseek-tui
crates.io
< 0.8.22
0.8.22
deepseek-tui-cli
crates.io
< 0.8.22
0.8.22
deepseek-tui
npm
< 0.8.22
0.8.22

References

Frequently Asked Questions

What is CVE-2026-45310?
CVE-2026-45310 is a security vulnerability in Deepseek tui involving DeepSeek TUI has SSRF via HTTP Redirect Bypass in fetch_url Tool under CWE-918: Server-Side Request Forgery (SSRF).
Which Deepseek tui versions are affected?
Affected versions include releases prior to 0.8.22 across affected packages: deepseek-tui, deepseek-tui-cli.
What version fixes CVE-2026-45310?
Upgrading to 0.8.22 (or the latest patched release for your respective branch) resolves the vulnerability.
Is deepseek-tui affected?
Yes, deepseek-tui is affected in releases prior to 0.8.22. Upgrade your dependency to 0.8.22 or later.
Is deepseek-tui-cli affected?
Yes, deepseek-tui-cli is affected in releases prior to 0.8.22. Upgrade your dependency to 0.8.22 or later.
What is the CVSS score of CVE-2026-45310?
CVE-2026-45310 has a CVSS v3.1 base score of 7.4 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-45310?
CVE-2026-45310 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check crates.io dependencies for CVE-2026-45310?
Run the dependency tree command: 'inspect dependencies for deepseek-tui'. 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-96ff-gc8g-wpvg",
  "modified" : "2026-06-09T10:19:44Z",
  "published" : "2026-05-14T20:29:26Z",
  "aliases" : [ "CVE-2026-45310" ],
  "summary" : "DeepSeek TUI has SSRF via HTTP Redirect Bypass in fetch_url Tool",
  "details" : "### Summary\nThe `fetch_url` tool validates the initial URL's resolved IP address against a restricted-IP blocklist (`is_restricted_ip()`) to prevent SSRF attacks against internal services (cloud metadata endpoints, localhost, private networks). However, the HTTP client (`reqwest`) is configured to automatically follow up to 5 redirects (`reqwest::redirect::Policy::limited(5)`) without re-validating the redirect target against the same SSRF protections.\n\n### PoC\n**Step 1 — Baseline:** Confirm `fetch_url` blocks direct requests to restricted IPs.\n```\nPrompt: use fetch_url to fetch http://169.254.169.254/latest/meta-data/\nExpected: Error — \"restricted address (private/loopback/link-local)\"\n```\n\n**Step 2 — SSRF bypass via redirect:** Fetch a public URL that redirects to the restricted IP.\n\n```\nPrompt: use fetch_url to fetch http://httpbin.org/redirect-to?url=http://169.254.169.254/latest/meta-data/&status_code=302\n```\n\n**Expected result:** The error message says \"connection refused\" or \"request failed: connect error\" — NOT \"restricted address.\" This proves the SSRF filter was bypassed; the connection failed only because `169.254.169.254` is unreachable from a non-cloud machine.\n\n**Observed result:** `fetch_url` followed the 302 redirect and attempted to connect to `169.254.169.254`. The error was a TCP-level connection failure, confirming the application-layer SSRF check was not applied to the redirect target.\n\n**Step 3 — Redirect to attacker-controlled host:** Confirm attacker-controlled redirect targets are followed.\n\n```\nPrompt: use fetch_url to fetch http://httpbin.org/redirect-to?url=http://[collaborator-domain]/ssrf-redirect-bypass&status_code=302\nExpected: Collaborator receives HTTP callback at /ssrf-redirect-bypass, confirming the redirect was followed.\n```\n\n### Impact\nOn cloud-hosted instances (AWS, GCP, Azure), an attacker can exfiltrate cloud IAM credentials, instance metadata, and other sensitive internal service data by redirecting `fetch_url` to `http://169.254.169.254/latest/meta-data/`. The attack is triggered via prompt injection (malicious instructions embedded in files or web content the model processes) that cause the model to call `fetch_url` with an attacker-controlled URL.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "deepseek-tui-cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8.22"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-96ff-gc8g-wpvg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/DeepSeek-TUI/security/advisories/GHSA-96ff-gc8g-wpvg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45310"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Hmbown/DeepSeek-TUI"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/DeepSeek-TUI/releases/tag/v0.8.22"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-14T20:29:26Z",
    "nvd_published_at" : "2026-05-28T18:16:35Z"
  }
}