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

CVE-2026-45373

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.26, although SSRF is validated against hostnames that resolve to private IPv6 addresses, when providing the IPV6 in‌‌ URL‌ as http://[::1], the SSRF defenses do not work. This vulnerability is fixed in 0.8.26.

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

CodeWhale coding agent prior to version 0.8.26 has an SSRF bypass vulnerability where IPv6 loopback addresses in bracket notation (http://[::1]) bypass SSRF defenses that correctly block hostnames resolving to private IPv6 addresses. This allows attackers to make the server request internal resources.

MitigationUpgrade to CodeWhale version 0.8.26 or later which contains the fix for this IPv6 URL format bypass.

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 show codewhale, npm list codewhale, etc.)
    Affected if The installed version is lower than 0.8.26 (e.g., 0.8.25, 0.8.0, etc.)
  2. Locate CodeWhale configuration files
    Look for config files named codewhale.conf, settings.py, config.json, or .env in the installation directory or working directory
    Affected if Configuration files exist and the application processes external URLs or hosts user-supplied URLs
  3. Check if SSRF protection is configured
    Inspect configuration files for keywords like 'ssrf', 'url_whitelist', 'allowed_hosts', 'request_validation', or 'internal_ip_block'
    Affected if SSRF protection is enabled and relies on blocking private IPv6 addresses but does not explicitly handle bracket notation like [::1]
  4. Test URL handling with IPv6 loopback format
    If the application accepts URL input, submit a request containing 'http://[::1]' or 'http://[::1]:<internal_port>' to see if it reaches internal resources
    Affected if The application successfully makes requests to http://[::1] despite having SSRF defenses that block other private IPv6 representations
  5. Review server-side request logs
    Check application logs for outgoing HTTP requests. Look for entries involving ::1, [::1], or other loopback IPv6 formats
    Affected if Outbound requests to IPv6 loopback addresses in bracket notation are logged and were not blocked by existing SSRF controls

You are affected if CodeWhale version is below 0.8.26 AND the application accepts URLs that it processes server-side, allowing an attacker to bypass SSRF defenses using http://[::1] notation.

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.26 or later which contains the fix for this IPv6 URL format bypass.

Recommended fix Moderate confidence

0.8.26

  1. 1. Check your current CodeWhale version by running: codewhale --version
  2. 2. If the version is earlier than 0.8.26, upgrade to version 0.8.26
  3. 3. Use your package manager or installation method to upgrade: pip install --upgrade codewhale (or follow your specific installation method)
  4. 4. Verify the upgrade was successful by running: codewhale --version
  5. 5. Confirm the version now shows 0.8.26 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45373 — 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-45373 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