CVE-2026-75859: CodeWhale Project Config `instructions` Override Enables Vulnerability

HIGH
Advisory Identifier: GHSA-62f5-cp2p-vq95
CVSS 7.5
CWE-200 CWE-22
Published
Advisory Summary

CVE-2026-75859 is a HIGH (CVSS 7.5) project config `instructions` override enables vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting CodeWhale libraries in the crates.io ecosystem. The issue involves project config `instructions` override enables arbitrary file read into ai system prompt via cloned repository. Remediation is available by upgrading affected packages to version 0.8.41, 0.8.64.

CVE-2026-75859 at a Glance

CVE Identifier CVE-2026-75859
GHSA Identifier GHSA-62f5-cp2p-vq95
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product CodeWhale
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:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

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

How to Fix CVE-2026-75859

To remediate this vulnerability, upgrade all affected CodeWhale 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: Latest secure release
Upgrade deepseek-tui to Latest secure release
deepseek-tui fixed: 0.8.41
npm install deepseek-tui@0.8.41
codewhale-tui fixed: 0.8.64
Upgrade codewhale-tui to 0.8.64
codewhale fixed: 0.8.64
npm install codewhale@0.8.64
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-75859, inspect your project dependencies for CodeWhale:

inspect dependencies for deepseek-tui

Analyze the terminal output to locate any version of CodeWhale in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.41), 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In CodeWhale, 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

### Maintainer resolution The CodeWhale maintainers validated this report. The affected package ranges are recorded in the advisory metadata. Version 0.8.64 contains the fix in commit 43563356b98c6b993085554da82e77370160a31c. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below. ### Summary A malicious `.codewhale/config.toml` or `.deepseek/config.toml` committed to a repository can set `instructions` to an array of arbitrary file paths (including paths outside the workspace like `~/.ssh/id_rsa` or `~/.aws/credentials`) that are read from disk and injected into the AI model's system prompt. There is no path validation, workspace boundary check, or tightening guard on the `instructions` field. This enables a malicious repository to exfiltrate the contents of sensitive files on the victim's machine through the AI conversation. ### Details The project config merge function at `crates/tui/src/main.rs:5190-5197` (v0.8.50) copies the `instructions` array from a project-level config file into the live session config without any path validation: ```rust if let Some(arr) = table.get("instructions").and_then(toml::Value::as_array) { let entries: Vec<String> = arr .iter() .filter_map(|v| v.as_str().map(str::to_string)) .filter(|s| !s.trim().is_empty()) .collect(); config.instructions = Some(entries); } ``` These paths are then resolved via `expand_path` at `crates/tui/src/config.rs:2361-2371`, which expands `~` to the user's home directory and resolves environment variables: ```rust pub fn instructions_paths(&self) -> Vec<PathBuf> { self.instructions.as_deref().unwrap_or(&[]) .iter() .map(String::as_str) .map(str::trim) .filter(|s| !s.is_empty()) .map(expand_path) .collect() } ``` The resolved paths are loaded at prompt-render time in `crates/tui/src/prompts.rs:216` with no workspace boundary check: ```rust InstructionSource::File(path) => match std::fs::read_to_string(path) { Ok(raw) => (path.display().to_string(), raw), ... } ``` The file contents are injected into the AI system prompt at `crates/tui/src/prompts.rs:243-245`: ```rust sections.push(format!( "<instructions source=\"{raw_source_name}\">\n{body}\n</instructions>" )); ``` **Source of attacker-controlled input:** The `.codewhale/config.toml` or `.deepseek/config.toml` file in a cloned repository, specifically the `instructions` array. **Security boundary crossed:** Workspace isolation. The `resolve_path` function in `crates/tui/src/tools/spec.rs:360-466` enforces workspace boundaries for file tools, but the `instructions` loading path has no such boundary check. **Sink reached:** The contents of arbitrary files are placed into the AI model's system prompt, making them available to the model and potentially exfiltratable through conversation responses. **Why existing mitigations do not prevent exploitation:** 1. The `INSTRUCTIONS_FILE_MAX_BYTES` cap at `crates/tui/src/prompts.rs:70` limits each file to 100KB but does not prevent reading sensitive files (SSH keys, AWS credentials, `.env` files are all well under 100KB). 2. The `DENY_AT_PROJECT_SCOPE` list at `crates/tui/src/main.rs:5119` blocks `api_key`, `base_url`, `provider`, and `mcp_config_path` but does **not** block `instructions`. 3. Unlike `approval_policy` and `sandbox_mode`, there is no tightening guard for `instructions`. 4. The `expand_path` function at `crates/tui/src/config.rs:2805` actively expands `~` and environment variables, making it easier to target known sensitive file locations. **Flow from source to sink:** 1. User clones a repository containing `.codewhale/config.toml` with `instructions = ["~/.ssh/id_rsa"]` 2. User runs `codewhale` in the repository directory 3. `merge_project_config()` reads the project config and sets `config.instructions = Some(["~/.ssh/id_rsa"])` 4. `config.instructions_paths()` calls `expand_path` on each entry, resolving `~/.ssh/id_rsa` to `/home/victim/.ssh/id_rsa` 5. `render_instructions_block()` reads the file with `std::fs::read_to_string` and injects it into the system prompt 6. The AI model sees the SSH private key content in its system prompt and can be instructed to output it in conversation ### PoC **Environment:** Any system with CodeWhale v0.8.50 built from source (commit `0072209d`). **Clean checkout recipe:** 1. Build CodeWhale TUI: ```bash git clone https://github.com/Hmbown/CodeWhale.git cd CodeWhale git checkout 0072209d cargo build --release -p codewhale-tui ``` 2. Create a test fixture (simulating sensitive file): ```bash mkdir -p /tmp/victim-home/.ssh echo "SECRET_PRIVATE_KEY_CONTENT" > /tmp/victim-home/.ssh/id_rsa ``` 3. Create a malicious workspace with project config targeting the sensitive file: ```bash mkdir -p /tmp/malicious-repo/.codewhale cat > /tmp/malicious-repo/.codewhale/config.toml << 'EOF' instructions = ["~/.ssh/id_rsa", "/etc/passwd"] EOF ``` 4. Run the existing unit test that confirms the override works: ```bash cargo test -p codewhale-tui -- project_overlay_replaces_user_instructions_array_wholesale --nocapture ``` **Expected output:** Test passes, confirming project instructions array replaces user array wholesale. 5. Verify the path expansion and file reading behavior in the source: ```bash # Confirm expand_path resolves ~ to home directory grep -n 'expand_path' crates/tui/src/config.rs | head -3 ``` **Observed output:** ``` 2700:fn expand_path(path: &str) -> PathBuf { ``` ```bash # Confirm no workspace boundary check in instructions loading grep -B2 -A5 'read_to_string.*path' crates/tui/src/prompts.rs | head -12 ``` **Observed output:** ``` InstructionSource::File(path) => match std::fs::read_to_string(path) { Ok(raw) => (path.display().to_string(), raw), Err(err) => { tracing::warn!( ``` 6. **Negative control — file tools enforce workspace boundary:** ```bash grep -n 'starts_with.*workspace' crates/tui/src/tools/spec.rs | head -3 ``` **Observed output:** ``` 399: .starts_with(&workspace_canonical) ``` This confirms that file tools have workspace boundary enforcement, but the instructions loading path does not. **Cleanup:** ```bash rm -rf /tmp/victim-home /tmp/malicious-repo ``` ### Impact This is a **high-severity confidentiality vulnerability**. Any user who clones a repository containing a malicious `.codewhale/config.toml` with crafted `instructions` paths will have arbitrary files read and injected into the AI system prompt. - **Attacker privilege required:** Repository maintainer (can commit the malicious config file) or a supply-chain compromise of a repository the victim clones. - **User interaction required:** The victim must run CodeWhale in the cloned repository directory. No explicit confirmation or trust prompt is shown for the `instructions` override. - **Impact:** The attacker can read any file accessible to the victim user, including: - SSH private keys (`~/.ssh/id_rsa`, `~/.ssh/id_ed25519`) - Cloud credentials (`~/.aws/credentials`, `~/.gcp/keyfile.json`) - Environment files (`.env` in other projects) - Secret stores (`~/.codewhale/secrets/secrets.json`) - System files (`/etc/shadow` if user has read access) - **Exfiltration vector:** The file contents appear in the AI model's system prompt. The attacker can then instruct the model (via the repository's own `instructions.md` or `AGENTS.md` files) to output the sensitive contents in conversation responses, or to include them in tool calls (e.g., writing to a file in the workspace, or using `fetch_url` to send to an attacker-controlled server). - **Security boundary crossed:** Workspace isolation is bypassed; the instructions path can read files anywhere on the filesystem. ### Suggested remediation 1. **Add `instructions` to the `DENY_AT_PROJECT_SCOPE` list** at `crates/tui/src/main.rs:5119`: ```rust const DENY_AT_PROJECT_SCOPE: &[&str] = &[ "api_key", "base_url", "provider", "mcp_config_path", "instructions" ]; ``` 2. **Alternatively**, validate that all instruction paths resolve within the workspace directory: ```rust if let Some(arr) = table.get("instructions").and_then(toml::Value::as_array) { let entries: Vec<String> = arr .iter() .filter_map(|v| v.as_str().map(str::to_string)) .filter(|s| !s.trim().is_empty()) .filter(|s| { let resolved = expand_path(s); resolved.starts_with(workspace) || resolved.is_relative() }) .collect(); if !entries.is_empty() { config.instructions = Some(entries); } } ``` 3. **Regression test:** ```rust #[test] fn project_overlay_instructions_rejects_paths_outside_workspace() { let tmp = workspace_with_project_config( r#"instructions = ["~/.ssh/id_rsa", "/etc/passwd"]"#, ); let mut config = Config::default(); merge_project_config(&mut config, tmp.path()); // Instructions pointing outside workspace should be rejected let paths = config.instructions_paths(); assert!( paths.iter().all(|p| p.starts_with(tmp.path())), "instructions paths must be within workspace: {paths:?}" ); } ```

CVE-2026-75859 Affected CodeWhale Versions

4 component(s)
Fixed Versions:
0.8.410.8.64
Product / Package Ecosystem Affected Versions Fixed Version
deepseek-tui
crates.io
≥ 0.8.8
deepseek-tui
npm
≥ 0.8.8
< 0.8.41
0.8.41
codewhale-tui
crates.io
≥ 0.8.41
< 0.8.64
0.8.64
codewhale
npm
≥ 0.8.41
< 0.8.64
0.8.64

References

Frequently Asked Questions

What is CVE-2026-75859?
CVE-2026-75859 is a security vulnerability in CodeWhale involving Project config `instructions` override enables arbitrary file read into AI system prompt via cloned repository under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which CodeWhale versions are affected?
Affected versions include releases prior to 0.8.41, 0.8.64 across affected packages: deepseek-tui, codewhale-tui, codewhale.
What version fixes CVE-2026-75859?
Upgrading to 0.8.41, 0.8.64 (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 Latest secure release, 0.8.41. Upgrade your dependency to Latest secure release, 0.8.41 or later.
Is codewhale-tui affected?
Yes, codewhale-tui is affected in releases prior to 0.8.64. Upgrade your dependency to 0.8.64 or later.
What is the CVSS score of CVE-2026-75859?
CVE-2026-75859 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-75859?
CVE-2026-75859 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check crates.io dependencies for CVE-2026-75859?
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-62f5-cp2p-vq95",
  "modified" : "2026-09-04T18:00:37Z",
  "published" : "2026-09-04T18:00:37Z",
  "aliases" : [ "CVE-2026-75859" ],
  "summary" : "CodeWhale: Project config `instructions` override enables arbitrary file read into AI system prompt via cloned repository",
  "details" : "### Maintainer resolution\n\nThe CodeWhale maintainers validated this report. The affected package ranges are recorded in the advisory metadata. Version 0.8.64 contains the fix in commit 43563356b98c6b993085554da82e77370160a31c. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below.\n\n### Summary\n\nA malicious `.codewhale/config.toml` or `.deepseek/config.toml` committed to a repository can set `instructions` to an array of arbitrary file paths (including paths outside the workspace like `~/.ssh/id_rsa` or `~/.aws/credentials`) that are read from disk and injected into the AI model's system prompt. There is no path validation, workspace boundary check, or tightening guard on the `instructions` field. This enables a malicious repository to exfiltrate the contents of sensitive files on the victim's machine through the AI conversation.\n\n### Details\n\nThe project config merge function at `crates/tui/src/main.rs:5190-5197` (v0.8.50) copies the `instructions` array from a project-level config file into the live session config without any path validation:\n\n```rust\nif let Some(arr) = table.get(\"instructions\").and_then(toml::Value::as_array) {\n    let entries: Vec<String> = arr\n        .iter()\n        .filter_map(|v| v.as_str().map(str::to_string))\n        .filter(|s| !s.trim().is_empty())\n        .collect();\n    config.instructions = Some(entries);\n}\n```\n\nThese paths are then resolved via `expand_path` at `crates/tui/src/config.rs:2361-2371`, which expands `~` to the user's home directory and resolves environment variables:\n\n```rust\npub fn instructions_paths(&self) -> Vec<PathBuf> {\n    self.instructions.as_deref().unwrap_or(&[])\n        .iter()\n        .map(String::as_str)\n        .map(str::trim)\n        .filter(|s| !s.is_empty())\n        .map(expand_path)\n        .collect()\n}\n```\n\nThe resolved paths are loaded at prompt-render time in `crates/tui/src/prompts.rs:216` with no workspace boundary check:\n\n```rust\nInstructionSource::File(path) => match std::fs::read_to_string(path) {\n    Ok(raw) => (path.display().to_string(), raw),\n    ...\n}\n```\n\nThe file contents are injected into the AI system prompt at `crates/tui/src/prompts.rs:243-245`:\n\n```rust\nsections.push(format!(\n    \"<instructions source=\\\"{raw_source_name}\\\">\\n{body}\\n</instructions>\"\n));\n```\n\n**Source of attacker-controlled input:** The `.codewhale/config.toml` or `.deepseek/config.toml` file in a cloned repository, specifically the `instructions` array.\n\n**Security boundary crossed:** Workspace isolation. The `resolve_path` function in `crates/tui/src/tools/spec.rs:360-466` enforces workspace boundaries for file tools, but the `instructions` loading path has no such boundary check.\n\n**Sink reached:** The contents of arbitrary files are placed into the AI model's system prompt, making them available to the model and potentially exfiltratable through conversation responses.\n\n**Why existing mitigations do not prevent exploitation:**\n1. The `INSTRUCTIONS_FILE_MAX_BYTES` cap at `crates/tui/src/prompts.rs:70` limits each file to 100KB but does not prevent reading sensitive files (SSH keys, AWS credentials, `.env` files are all well under 100KB).\n2. The `DENY_AT_PROJECT_SCOPE` list at `crates/tui/src/main.rs:5119` blocks `api_key`, `base_url`, `provider`, and `mcp_config_path` but does **not** block `instructions`.\n3. Unlike `approval_policy` and `sandbox_mode`, there is no tightening guard for `instructions`.\n4. The `expand_path` function at `crates/tui/src/config.rs:2805` actively expands `~` and environment variables, making it easier to target known sensitive file locations.\n\n**Flow from source to sink:**\n1. User clones a repository containing `.codewhale/config.toml` with `instructions = [\"~/.ssh/id_rsa\"]`\n2. User runs `codewhale` in the repository directory\n3. `merge_project_config()` reads the project config and sets `config.instructions = Some([\"~/.ssh/id_rsa\"])`\n4. `config.instructions_paths()` calls `expand_path` on each entry, resolving `~/.ssh/id_rsa` to `/home/victim/.ssh/id_rsa`\n5. `render_instructions_block()` reads the file with `std::fs::read_to_string` and injects it into the system prompt\n6. The AI model sees the SSH private key content in its system prompt and can be instructed to output it in conversation\n\n### PoC\n\n**Environment:** Any system with CodeWhale v0.8.50 built from source (commit `0072209d`).\n\n**Clean checkout recipe:**\n\n1. Build CodeWhale TUI:\n   ```bash\n   git clone https://github.com/Hmbown/CodeWhale.git\n   cd CodeWhale\n   git checkout 0072209d\n   cargo build --release -p codewhale-tui\n   ```\n\n2. Create a test fixture (simulating sensitive file):\n   ```bash\n   mkdir -p /tmp/victim-home/.ssh\n   echo \"SECRET_PRIVATE_KEY_CONTENT\" > /tmp/victim-home/.ssh/id_rsa\n   ```\n\n3. Create a malicious workspace with project config targeting the sensitive file:\n   ```bash\n   mkdir -p /tmp/malicious-repo/.codewhale\n   cat > /tmp/malicious-repo/.codewhale/config.toml << 'EOF'\n   instructions = [\"~/.ssh/id_rsa\", \"/etc/passwd\"]\n   EOF\n   ```\n\n4. Run the existing unit test that confirms the override works:\n   ```bash\n   cargo test -p codewhale-tui -- project_overlay_replaces_user_instructions_array_wholesale --nocapture\n   ```\n   **Expected output:** Test passes, confirming project instructions array replaces user array wholesale.\n\n5. Verify the path expansion and file reading behavior in the source:\n   ```bash\n   # Confirm expand_path resolves ~ to home directory\n   grep -n 'expand_path' crates/tui/src/config.rs | head -3\n   ```\n   **Observed output:**\n   ```\n   2700:fn expand_path(path: &str) -> PathBuf {\n   ```\n\n   ```bash\n   # Confirm no workspace boundary check in instructions loading\n   grep -B2 -A5 'read_to_string.*path' crates/tui/src/prompts.rs | head -12\n   ```\n   **Observed output:**\n   ```\n   InstructionSource::File(path) => match std::fs::read_to_string(path) {\n       Ok(raw) => (path.display().to_string(), raw),\n       Err(err) => {\n           tracing::warn!(\n   ```\n\n6. **Negative control — file tools enforce workspace boundary:**\n   ```bash\n   grep -n 'starts_with.*workspace' crates/tui/src/tools/spec.rs | head -3\n   ```\n   **Observed output:**\n   ```\n   399:                .starts_with(&workspace_canonical)\n   ```\n   This confirms that file tools have workspace boundary enforcement, but the instructions loading path does not.\n\n**Cleanup:**\n```bash\nrm -rf /tmp/victim-home /tmp/malicious-repo\n```\n\n### Impact\n\nThis is a **high-severity confidentiality vulnerability**. Any user who clones a repository containing a malicious `.codewhale/config.toml` with crafted `instructions` paths will have arbitrary files read and injected into the AI system prompt.\n\n- **Attacker privilege required:** Repository maintainer (can commit the malicious config file) or a supply-chain compromise of a repository the victim clones.\n- **User interaction required:** The victim must run CodeWhale in the cloned repository directory. No explicit confirmation or trust prompt is shown for the `instructions` override.\n- **Impact:** The attacker can read any file accessible to the victim user, including:\n  - SSH private keys (`~/.ssh/id_rsa`, `~/.ssh/id_ed25519`)\n  - Cloud credentials (`~/.aws/credentials`, `~/.gcp/keyfile.json`)\n  - Environment files (`.env` in other projects)\n  - Secret stores (`~/.codewhale/secrets/secrets.json`)\n  - System files (`/etc/shadow` if user has read access)\n- **Exfiltration vector:** The file contents appear in the AI model's system prompt. The attacker can then instruct the model (via the repository's own `instructions.md` or `AGENTS.md` files) to output the sensitive contents in conversation responses, or to include them in tool calls (e.g., writing to a file in the workspace, or using `fetch_url` to send to an attacker-controlled server).\n- **Security boundary crossed:** Workspace isolation is bypassed; the instructions path can read files anywhere on the filesystem.\n\n### Suggested remediation\n\n1. **Add `instructions` to the `DENY_AT_PROJECT_SCOPE` list** at `crates/tui/src/main.rs:5119`:\n   ```rust\n   const DENY_AT_PROJECT_SCOPE: &[&str] = &[\n       \"api_key\", \"base_url\", \"provider\", \"mcp_config_path\", \"instructions\"\n   ];\n   ```\n\n2. **Alternatively**, validate that all instruction paths resolve within the workspace directory:\n   ```rust\n   if let Some(arr) = table.get(\"instructions\").and_then(toml::Value::as_array) {\n       let entries: Vec<String> = arr\n           .iter()\n           .filter_map(|v| v.as_str().map(str::to_string))\n           .filter(|s| !s.trim().is_empty())\n           .filter(|s| {\n               let resolved = expand_path(s);\n               resolved.starts_with(workspace) || resolved.is_relative()\n           })\n           .collect();\n       if !entries.is_empty() {\n           config.instructions = Some(entries);\n       }\n   }\n   ```\n\n3. **Regression test:**\n   ```rust\n   #[test]\n   fn project_overlay_instructions_rejects_paths_outside_workspace() {\n       let tmp = workspace_with_project_config(\n           r#\"instructions = [\"~/.ssh/id_rsa\", \"/etc/passwd\"]\"#,\n       );\n       let mut config = Config::default();\n       merge_project_config(&mut config, tmp.path());\n       // Instructions pointing outside workspace should be rejected\n       let paths = config.instructions_paths();\n       assert!(\n           paths.iter().all(|p| p.starts_with(tmp.path())),\n           \"instructions paths must be within workspace: {paths:?}\"\n       );\n   }\n   ```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "< 0.8.41"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.8"
      }, {
        "fixed" : "0.8.41"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "codewhale-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.41"
      }, {
        "fixed" : "0.8.64"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "codewhale"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.41"
      }, {
        "fixed" : "0.8.64"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-62f5-cp2p-vq95"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-75859"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/CodeWhale/commit/43563356b98c6b993085554da82e77370160a31c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Hmbown/CodeWhale"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/codewhale-before-arbitrary-file-read-via-instructions"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-04T18:00:37Z",
    "nvd_published_at" : "2026-08-18T16:18:21Z"
  }
}