dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-45310

HIGH · 7.4 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CodeWhale is a DeepSeek + MiMo coding agent in terminal. Prior to 0.8.22, 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. This vulnerability is fixed in 0.8.22.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The fetch_url tool in CodeWhale validates only the initial URL's resolved IP against a restricted-IP blocklist (is_restricted_ip()) to prevent SSRF. However, reqwest is configured to follow up to 5 redirects automatically without re-validating redirect targets, allowing attackers to bypass the blocklist by using a benign external URL that redirects to internal services (cloud metadata endpoints, localhost, private networks).

MitigationUpgrade to CodeWhale version 0.8.22 or later, which implements validation of redirect targets against the same is_restricted_ip() blocklist used for initial URLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CodeWhale installation and version
    Run `codewhale --version` or check the installed package version via your package manager (pip, cargo, etc.)
    Affected if Version is below 0.8.22 (the fix implements redirect target validation)
  2. Locate fetch_url tool usage
    Search for imports or calls to 'fetch_url' in your codebase or CodeWhale configuration files
    Affected if The fetch_url tool is being used to make HTTP requests to user-controlled URLs
  3. Inspect reqwest redirect configuration
    Examine the CodeWhale source code or configuration for reqwest client setup; look for `.redirect(reqwest::redirect::Policy::limited(5))` or similar without custom redirect validation logic
    Affected if Redirects are set to follow automatically (default reqwest behavior) without validating each redirect target against the IP blocklist
  4. Check network exposure
    Verify if the CodeWhale instance has network access to internal services, cloud metadata endpoints (e.g., 169.254.169.254), or private network ranges
    Affected if The service can reach internal IPs or cloud metadata endpoints that could be targeted via redirect
  5. Review IP blocklist implementation
    Search the codebase for the `is_restricted_ip()` function and confirm it is only applied to the initial URL resolution, not to redirect targets
    Affected if The blocklist check is missing for redirect destinations, only applied to the initial URL

You are affected if CodeWhale version is below 0.8.22 AND the fetch_url tool is used to fetch URLs that could be redirected to internal services or private IPs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to CodeWhale version 0.8.22 or later, which implements validation of redirect targets against the same is_restricted_ip() blocklist used for initial URLs.

Recommended fix Moderate confidence

0.8.22

  1. Upgrade CodeWhale to version 0.8.22 or later to obtain the fixed code that validates redirect targets against SSRF protections

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45310 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data