Skip to content
AI/ML

CVE-2026-71281

8.8
High
EPSS 0.27%Aug 5, 2026

RCE via torch.load in Hugging Face peft LoRA-GA/CorDA

common questions

Is CVE-2026-71281 being exploited?

Not confirmed. CVE-2026-71281 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-71281?

CVE-2026-71281 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-71281?

Not known from our data. No patch reference has been recorded for CVE-2026-71281, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-71281 affect?

CVE-2026-71281 affects huggingface/peft (LoRA-GA module), huggingface/peft (CorDA module), Python ML workflows that load LoRA cache/covariance files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71281?

Do not load untrusted LoRA/CorDA files; enforce weights_only=True or sandbox loads; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
huggingface/peft (LoRA-GA module)huggingface/peft (CorDA module)Python ML workflows that load LoRA cache/covariance files
impact

Arbitrary code execution by deserializing malicious LoRA/CorDA cache or covariance files via torch.load without weights_only=True.

action required

Immediate action required

affected versions
huggingface peft
  • affected<= 0.19.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free