How severe is CVE-2015-1856?

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

Which packages are affected by CVE-2015-1856?

CVE-2015-1856 affects the following packages: swift (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-1856?

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

How do I detect CVE-2015-1856 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-2015-1856 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-2015-1856 actively exploited in the wild?

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

CVE-2015-1856 has an EPSS (Exploit Prediction Scoring System) score of 4.1%, placing it in the 91th 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-2015-1856?

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

When was CVE-2015-1856 published, and has it been updated?

CVE-2015-1856 was published on April 17, 2015 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-2015-1856 — swift

CVE-2015-1856 is a CWE-264 vulnerability in swift. A fix is available for swift — see the affected versions and patch details below.

OpenStack Swift Unauthorized delete of versioned Swift object

Also known asGHSA-cc77-5vw4-7pwgPYSEC-2026-931

Published

Apr 17, 2015

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.1%probability of exploitation in next 30 days

Lower Risk+0.11%

Lower risk than most CVEs91th percentile — riskier than 91% 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.3.0, when allow_version is configured, allows remote authenticated users to delete the latest version of an object by leveraging listing access to the x-versions-location container.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 4 configurations

ubuntu linuxcanonical

3 versions

12.0414.0415.04

Application

swiftopenstack

≤ 2.2.2

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.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1856 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 6 for Red Hat Storage	`glusterfs-0:3.7.1-16.el6`	RHSA-2015:1845
Native Client for RHEL 7 for Red Hat Storage	`glusterfs-0:3.7.1-16.el7`	RHSA-2015:1846
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-swift-0:1.13.1-6.el6ost`	RHSA-2015:1684
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-swift-0:2.2.0-4.el7ost`	RHSA-2015:1681

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-1856 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works