Security readout for executives and security teams
Plain-English summary
CVE-2026-45311 lets a malicious repository make CodeWhale run test code without asking the user. Because Rust tests, build scripts, and proc macros can execute code, this can lead to credential theft, persistence, or full host compromise when a user opens or works in a hostile repo.
Executive priority
Prioritize remediation for developer machines handling source code, secrets, or customer systems. The business risk is high because normal agent behavior can become code execution without an approval prompt.
Technical view
CodeWhale versions >=0.3.0 and <0.8.23 run the run_tests tool with ApprovalRequirement::Auto, executing cargo test without approval. cargo test can compile and execute arbitrary repository code, including test binaries, build.rs scripts, and proc macros. AGENTS.md auto-loading can increase risk by prompting proactive test execution.
Likely exposure
Exposure is likely limited to teams using CodeWhale versions before 0.8.23, especially on developer workstations or CI-like environments that open untrusted or external repositories.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. Exploitation requires user interaction with a malicious repository, but no further privilege is required once CodeWhale auto-runs tests in that workspace.
Researcher notes
The core boundary issue is auto-approved test execution in a coding agent. Evidence supports arbitrary code execution through Rust test/build mechanisms and AGENTS.md prompt influence, but sources do not provide exploit telemetry or broader product impact.
Mitigation direction
- Upgrade CodeWhale to version 0.8.23 or later.
- Avoid using affected CodeWhale versions with untrusted repositories.
- Do not run affected versions where developer credentials or production secrets are available.
- Review the GitHub advisory for any updated vendor guidance.
- Treat exposed tokens as potentially compromised if tests ran in a malicious workspace.
Validation and detection
- Inventory CodeWhale installations and identify versions >=0.3.0 and <0.8.23.
- Confirm upgraded systems report CodeWhale version 0.8.23 or later.
- Review session history for automatic run_tests or cargo test execution in untrusted repositories.
- Check whether affected sessions had access to credentials, tokens, SSH keys, or cloud secrets.
- Look for unexpected persistence or outbound activity after suspicious CodeWhale sessions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45311 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-wx44-2q6h-j6p8CVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.