CARGO · SEPTEMBER 2026 · EARLY WARNING

CodeWhale Arbitrary File Read Vulnerability: Early Warning

Q: Am I affected?

You are affected if you are using codewhale (cargo) version 0.8.22 or earlier, or any version between 0.8.21 and 0.8.0, or any version between 0.7.9 and 0.7.0, or any version between 0.6.7 and 0.6.0, or any version between 0.5.2 and 0.5.0, or any version between 0.4.9 and 0.4.0, or any version between 0.3.33 and 0.3.0.

Q: What should I do right now?

Upgrade to CodeWhale version 0.8.64 or later to mitigate the vulnerability.

Q: Has this been exploited in the wild?

There is no indication that this vulnerability has been exploited in the wild at this time.

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

Severity: HIGH
Affected component: codewhale (cargo)
Affected versions: >= v0.8.22, <= v0.8.22 or >= v0.8.21, <= v0.8.21 or >= v0.8.20, <= v0.8.20 or >= v0.8.19, <= v0.8.19 or >= v0.8.18, <= v0.8.18 or >= v0.8.17, <= v0.8.17 or >= v0.8.15, <= v0.8.15 or >= v0.8.14, <= v0.8.14 or >= v0.8.13, <= v0.8.13 or >= v0.8.12, <= v0.8.12 or >= v0.8.11, <= v0.8.11 or >= v0.8.10, <= v0.8.10 or >= v0.8.9, <= v0.8.9 or >= v0.8.8, <= v0.8.8 or >= v0.8.7, <= v0.8.7 or >= v0.8.6, <= v0.8.6 or >= v0.8.5, <= v0.8.5 or >= v0.8.4, <= v0.8.4 or >= v0.8.3, <= v0.8.3 or >= v0.8.2, <= v0.8.2 or >= v0.8.1, <= v0.8.1 or >= v0.8.0, <= v0.8.0 or >= v0.7.9, <= v0.7.9 or >= v0.7.8, <= v0.7.8 or >= v0.7.7, <= v0.7.7 or >= v0.7.6, <= v0.7.6 or >= v0.7.5, <= v0.7.5 or >= v0.7.4, <= v0.7.4 or >= v0.7.2, <= v0.7.2 or >= v0.7.1, <= v0.7.1 or >= v0.7.0, <= v0.7.0 or >= v0.6.7, <= v0.6.7 or >= v0.6.6, <= v0.6.6 or >= v0.6.5, <= v0.6.5 or >= v0.6.4, <= v0.6.4 or >= v0.6.3, <= v0.6.3 or >= v0.6.2, <= v0.6.2 or >= v0.6.1, <= v0.6.1 or >= v0.5.2, <= v0.5.2 or >= v0.5.1, <= v0.5.1 or >= v0.5.0, <= v0.5.0 or >= v0.4.9, <= v0.4.9 or >= v0.4.8, <= v0.4.8 or >= v0.4.7, <= v0.4.7 or >= v0.4.6, <= v0.4.6 or >= v0.4.5, <= v0.4.5 or >= v0.4.4, <= v0.4.4 or >= v0.4.3, <= v0.4.3 or >= v0.4.2, <= v0.4.2 or >= v0.4.1, <= v0.4.1 or >= v0.4.0, <= v0.4.0 or >= v0.3.33, <= v0.3.33 or >= v0.3.32, <= v0.3.32 or >= v0.3.31, <= v0.3.31 or >= v0.3.28, <= v0.3.28 or >= v0.3.27, <= v0.3.27 or >= v0.3.26, <= v0.3.26 or >= v0.3.25, <= v0.3.25 or >= v0.3.24, <= v0.3.24 or >= v0.3.23, <= v0.3.23 or >= v0.3.22, <= v0.3.22 or >= v0.3.21, <= v0.3.21 or >= v0.3.20, <= v0.3.20 or >= v0.3.19, <= v0.3.19 or >= v0.3.18, <= v0.3.18 or >= v0.3.17, <= v0.3.17 or >= v0.3.16, <= v0.3.16 or >= v0.3.14, <= v0.3.14 or >= v0.3.13, <= v0.3.13 or >= v0.3.12, <= v0.3.12 or >= v0.3.11, <= v0.3.11 or >= v0.3.10, <= v0.3.10 or >= v0.3.5, <= v0.3.5 or >= v0.3.4, <= v0.3.4 or >= v0.3.3, <= v0.3.3 or >= v0.3.2, <= v0.3.2 or >= v0.3.1, <= v0.3.1 or >= v0.3.0, <= v0.3.0
Patched version: 0.8.64

CVE-2026-45311GHSA-C6MW-8XH8-GPQ6

An early warning has been issued for a high-severity vulnerability in the CodeWhale tool. The vulnerability, which allows arbitrary file read, affects multiple versions of the codewhale (cargo) component.

What happened

The vulnerability in question is tracked as CVE-2026-45311 and GHSA-C6MW-8XH8-GPQ6. It was first flagged on 2026-09-04T18:11:45+00:00. The issue lies in the `git_blame` tool within DeepSeek-TUI, which permits arbitrary file read due to unvalidated input. This can potentially lead to the exfiltration of sensitive files such as SSH keys and environment variables.

The vulnerability is reportedly not yet exploited in the wild, and there is no indication of a supply-chain attack. However, the severity is rated as high, and immediate action is recommended to mitigate potential risks.

What to do about it

Upgrade to CodeWhale version 0.8.64 or later to address the arbitrary file read vulnerability.
Review your project configurations and ensure that any overrides or custom settings do not inadvertently expose sensitive files.
Monitor the primary sources for updates on the vulnerability and any additional mitigation steps that may be recommended.

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If codewhale is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using codewhale (cargo) version 0.8.22 or earlier, or any version between 0.8.21 and 0.8.0, or any version between 0.7.9 and 0.7.0, or any version between 0.6.7 and 0.6.0, or any version between 0.5.2 and 0.5.0, or any version between 0.4.9 and 0.4.0, or any version between 0.3.33 and 0.3.0.

What should I do right now?

Upgrade to CodeWhale version 0.8.64 or later to mitigate the vulnerability.

Has this been exploited in the wild?

There is no indication that this vulnerability has been exploited in the wild at this time.

Sources

Join the 0Day waitlist →

← Back to all threats