CVE-2005-3008: Tofu 0.2 allows remote attackers to execute arbitrary Python code via crafted pickled objects, which Tofu unpi
CVE-2005-3008 is a high-severity flaw (CVSS 7.5) affecting tofu. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Tofu 0.2 allows remote attackers to execute arbitrary Python code via crafted pickled objects, which Tofu unpickles and executes.
Why this priority
- High severity
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| EPSS exploit chance | 1.5% (top 25%) |
| CISA exploited list | No |
| Published | 2005-09-21 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2005-3008?
tofu: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2005-3008 being exploited?
CVE-2005-3008 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2005-3008 affect?
CVE-2005-3008 affects tofu. Severity is high (CVSS 7.5). Tofu 0.2 allows remote attackers to execute arbitrary Python code via crafted pickled objects, which Tofu unpickles and executes.
How urgent is CVE-2005-3008?
Priority 45/100. High severity