# CVE-2026-15605: wandb Artifact Integrity Validation hashutil.py ArtifactManifestEntry.download weak hash

> Attackers can bypass artifact integrity checks in the wandb SDK due to the use of a weak hash algorithm during downloads.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-hq6h-q7pr-4qqv

## What is CVE-2026-15605?

CVE-2026-15605 is a low-severity vulnerability in wandb, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in wandb 0.25.2.dev1. Affected is the function ArtifactManifestEntry.download in the library wandb/sdk/lib/hashutil.py of the component Artifact Integrity Validation. The manipulation leads to use of weak hash. The attack may be initiated remotely. A high degree of complexity is needed for the attack. The exploitability is told to be difficult. The pull request to fix this issue awaits acceptance.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2026-15605?


## How do I fix CVE-2026-15605?

No fix has been published for CVE-2026-15605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15605 being exploited?

There is no known exploitation of CVE-2026-15605 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15605 and fix it if it is affected.

What it is: CVE-2026-15605 is a low-severity vulnerability in wandb, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15605 in the wild and no public exploit code.

Affected product: wandb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15605/ (Markdown: https://insights.sbomify.com/CVE-2026-15605/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15605
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15605
- OSV: https://osv.dev/vulnerability/CVE-2026-15605

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15605/
Summaries are generated and may contain mistakes; the official description above is the record.