# CVE-2026-71281: peft Unsafe Deserialization via torch.load() Without weights_only in LoRA-GA and CorDA Modules

> Attackers can execute arbitrary code by providing malicious cache files to peft's LoRA-GA and CorDA modules due to unsafe torch.load usage.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-g7pc-47rc-wvwf

## What is CVE-2026-71281?

CVE-2026-71281 is a high-severity unsafe deserialization vulnerability in huggingface peft, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hugging Face peft's LoRA-GA and CorDA initialization modules (src/peft/tuners/lora/corda.py lines ~102 and ~163, and src/peft/tuners/lora/loraga.py line ~101) call torch.load on config-specified cache/covariance files without weights_only=True, bypassing peft's own safe-loading wrapper used elsewhere in the codebase.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-71281 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71281 is a high-severity unsafe deserialization vulnerability in huggingface peft, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71281 in the wild and no public exploit code.

Affected product: huggingface peft. 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-71281/ (Markdown: https://insights.sbomify.com/CVE-2026-71281/index.md)
```

## Sources

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

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