How severe is CVE-2016-0737?

CVE-2016-0737 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-0737?

CVE-2016-0737 affects the following packages: swift (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2016-0737?

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

How do I detect CVE-2016-0737 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-2016-0737 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2016-0737 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-0737 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-2016-0737?

CVE-2016-0737 has an EPSS (Exploit Prediction Scoring System) score of 3.8%, placing it in the 90th 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-2016-0737?

CVE-2016-0737 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-2016-0737 published, and has it been updated?

CVE-2016-0737 was published on January 29, 2016 and was last updated on October 24, 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

HIGH severity

CVE-2016-0737 — swift

HIGH

CVE-2016-0737 is a high-severity (CVSS 7.5) CWE-399 vulnerability in swift. A fix is available for swift — see the affected versions and patch details below.

OpenStack Object Storage (Swift) allows remote attackers to cause a denial of service

Also known asGHSA-972c-cfv8-2hq8PYSEC-2026-929

Published

Jan 29, 2016

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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.4.0 does not properly close client connections, which allows remote attackers to cause a denial of service (proxy-server resource consumption) via a series of interrupted requests to a Large Object URL.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

swiftopenstack

≤ 2.3.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.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0737 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-swift-0:1.13.1-8.el6ost`	RHSA-2016:0126
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-swift-0:1.13.1-8.el7ost`	RHSA-2016:0127
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-swift-0:2.2.0-6.el7ost`	RHSA-2016:0128
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7	`openstack-swift-0:2.3.0-3.el7ost`	RHSA-2016:0155
Red Hat Gluster Storage 3.1 for RHEL 6	`openstack-swift-0:1.13.1-8.el6ost`	RHSA-2016:0329
Red Hat Gluster Storage 3.1 for RHEL 7	`openstack-swift-0:1.13.1-8.el7ost`	RHSA-2016:0328

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-0737 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works