CVE-2012-4406

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 4.7%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

OpenStack Object Storage (swift) before 1.7.0 uses the loads function in the pickle Python module unsafely when storing and loading metadata in memcached, which allows remote attackers to execute arbitrary code via a crafted pickle object.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
93.0%
KEV
Not listed

Published

October 22, 2012

Last Modified

April 29, 2026

Advisory Details (9)

Auto-updated May 10, 2026
Patch available. Sources: redhat.
generic

Do not use pickle for serialization in memcache, but JSON · openstack/swift@e1ff51c · GitHub

https://github.com/openstack/swift/commit/e1ff51c04554d51616d2845f92ab726cb0e5831a
redhat Patch Available

854757 – (CVE-2012-4406) CVE-2012-4406 Openstack-Swift: insecure use of python pickle()

https://bugzilla.redhat.com/show_bug.cgi?id=854757
generic

Bug #1006414 “Insecure loads()” : Bugs : OpenStack Object Storage (swift)

https://bugs.launchpad.net/swift/+bug/1006414
generic

oss-security - CVE-Request: openstack pickle de-serialization

http://www.openwall.com/lists/oss-security/2012/09/05/4
generic

oss-security - Re: CVE-Request: openstack pickle de-serialization

http://www.openwall.com/lists/oss-security/2012/09/05/16

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-swift (1.8.0-0ubuntu1.2) @ raring2026-05-20ubuntu
redhatvdsm-0:4.9.6-20.el6rhs2013-03-28redhat
redhatopenstack-swift-0:1.4.8-5.el62012-10-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
swift1.0.21.7.0

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 14:01 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-28 14:03 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-25 13:46 UTCEPSS rescore
  17. 2026-06-25 13:46 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:22 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-21 01:56 UTCEPSS rescore
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-19 21:52 UTCOSV refresh
Show 72 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-16 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-15 17:44 UTCEPSS rescore
  8. 2026-06-14 23:14 UTCEPSS rescore
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-12 23:08 UTCEPSS rescore
  12. 2026-06-11 13:56 UTCEPSS rescore
  13. 2026-06-10 22:14 UTCEPSS rescore
  14. 2026-06-10 13:18 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-08 14:14 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 01:25 UTCOSV refresh
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-31 00:14 UTCEPSS rescore
  31. 2026-05-29 13:41 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-27 13:38 UTCEPSS rescore
  35. 2026-05-27 13:38 UTCEPSS rescore
  36. 2026-05-26 13:41 UTCEPSS rescore
  37. 2026-05-26 13:41 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-24 16:43 UTCEPSS rescore
  42. 2026-05-23 00:10 UTCEG score recompute
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-22 21:15 UTCEPSS rescore
  45. 2026-05-22 21:15 UTCEPSS rescore
  46. 2026-05-21 22:39 UTCEPSS rescore
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-20 11:21 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-20 10:17 UTCEG score recompute
  54. 2026-05-20 10:17 UTCVendor advisory
  55. 2026-05-20 06:10 UTCEG score recompute
  56. 2026-05-20 06:10 UTCVendor advisory
  57. 2026-05-20 02:02 UTCEG score recompute
  58. 2026-05-20 02:02 UTCVendor advisory
  59. 2026-05-19 21:54 UTCEG score recompute
  60. 2026-05-19 21:54 UTCVendor advisory
  61. 2026-05-19 17:46 UTCEG score recompute
  62. 2026-05-19 17:46 UTCVendor advisory
  63. 2026-05-19 13:39 UTCEG score recompute
  64. 2026-05-19 13:39 UTCVendor advisory
  65. 2026-05-19 09:30 UTCEG score recompute
  66. 2026-05-19 09:30 UTCVendor advisory
  67. 2026-05-19 05:23 UTCEG score recompute
  68. 2026-05-19 05:23 UTCVendor advisory
  69. 2026-05-19 01:17 UTCEG score recompute
  70. 2026-05-19 01:17 UTCVendor advisory
  71. 2026-05-18 21:29 UTCEPSS rescore
  72. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2012-4406?
CVE-2012-4406 is a critical vulnerability published on October 22, 2012. OpenStack Object Storage (swift) before 1.7.0 uses the loads function in the pickle Python module unsafely when storing and loading metadata in memcached, which allows remote attackers to execute arbitrary code via a crafted pickle object.
When was CVE-2012-4406 disclosed?
CVE-2012-4406 was first published in the National Vulnerability Database on October 22, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-4406 actively exploited?
CVE-2012-4406 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2012-4406?
CVE-2012-4406 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2012-4406?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-4406, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-4406

Explore →

Is Your Infrastructure Affected by CVE-2012-4406?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.