How severe is CVE-2014-7960?

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

Which packages are affected by CVE-2014-7960?

CVE-2014-7960 affects the following packages: swift (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-7960?

Update swift to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-7960 is resolved across your whole dependency graph.

How do I detect CVE-2014-7960 in my PyPI dependencies?

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

How do I mitigate CVE-2014-7960 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-2014-7960 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-7960 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-7960?

CVE-2014-7960 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 88th 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-2014-7960?

CVE-2014-7960 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-7960 published, and has it been updated?

CVE-2014-7960 was published on October 17, 2014 and was last updated on July 7, 2026. 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-2014-7960 — swift

Fix: openstack/swift@06800cb

CVE-2014-7960 is a CWE-399 vulnerability in swift. A fix is available for swift — see the affected versions and patch details below.

OpenStack Swift metadata constraints are not correctly enforced

Also known asGHSA-g6x3-55qv-x6p2PYSEC-2026-933

Published

Oct 17, 2014

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍swift

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

OpenStack Object Storage (Swift) before 2.2.0 allows remote authenticated users to bypass the max_meta_count and other metadata constraints via multiple crafted requests which exceed the limit when combined.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`swift`	all versions	2.2.0`pip install --upgrade 'swift==2.2.0'`

Affected Products

1 product · 1 configurations

Application

swiftopenstack

≤ 2.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update swift to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-7960 is resolved across your whole dependency graph.
Workarounds
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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Native Client for RHEL 5 for Red Hat Storage	`glusterfs-0:3.7.1-11.el5`	RHSA-2015:1495
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-swift-0:1.13.1-4.el6ost`	RHSA-2015:0836
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-swift-0:1.13.1-4.el7ost`	RHSA-2015:0835

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-7960 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works