How severe is CVE-2012-0051?

No CVSS score has been assigned to CVE-2012-0051 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-0051?

CVE-2012-0051 affects the following packages: tahoe-lafs (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2012-0051?

The records we use list no patched version of tahoe-lafs for CVE-2012-0051. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2012-0051 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tahoe-lafs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-0051 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2012-0051 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2012-0051, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-0051?

CVE-2012-0051 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-0051?

CVE-2012-0051 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-0051 published, and has it been updated?

CVE-2012-0051 was published on April 23, 2022 and was last updated on November 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2012-0051 — tahoe-lafs

CVE-2012-0051 is a Improper Input Validation vulnerability in tahoe-lafs. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Tahoe-LAFS fails to ensure integrity

Published

Apr 23, 2022

Updated

Nov 22, 2024

Affected

1 pkg

Patched

See advisory

Exploits

2 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍tahoe-lafs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers to corrupt mutable files or directories upon retrieval.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tahoe-lafs`	all versions	No fix

Affected Products

2 products · 4 configurations

debian linuxdebian

3 versions

8.09.010.0

Application

tahoe-lafstahoe-lafs

1 version

1.9.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers…

openwall.comNVDNov 2019

Report on tahoe-lafs.org

tahoe-lafs.orgNVDNov 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tahoe-lafs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of tahoe-lafs for CVE-2012-0051. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers to corrupt mutable files or directories upon retrieval.

O3 Security · Impact-Aware SCA

Is CVE-2012-0051 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works