What is CVE-2015-1856?

CVE-2015-1856 is a medium-severity security vulnerability in swift (pip), affecting versions < 2.3.0. It is fixed in 2.3.0.

Which versions of swift are affected by CVE-2015-1856?

swift (pip) versions < 2.3.0 is affected.

Is there a fix for CVE-2015-1856?

Yes. CVE-2015-1856 is fixed in 2.3.0. Upgrade to this version or later.

Is CVE-2015-1856 exploitable, and should I be worried?

Whether CVE-2015-1856 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2015-1856 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2015-1856 in swift

Q: Which versions of swift are affected by CVE-2015-1856?

swift (pip) versions < 2.3.0 is affected.

Q: Is there a fix for CVE-2015-1856?

Yes. CVE-2015-1856 is fixed in 2.3.0. Upgrade to this version or later.

Q: Is CVE-2015-1856 exploitable, and should I be worried?

Whether CVE-2015-1856 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2015-1856 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2015-1856?

Upgrade swift to 2.3.0 or later.

Summary

OpenStack Swift Unauthorized delete of versioned Swift object

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.

Impact

Affected versions

swift (< 2.3.0)

Security releases

swift → 2.3.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade swift to 2.3.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2015-1856? CVE-2015-1856 is a medium-severity security vulnerability in swift (pip), affecting versions < 2.3.0. It is fixed in 2.3.0.
Which versions of swift are affected by CVE-2015-1856? swift (pip) versions < 2.3.0 is affected.
Is there a fix for CVE-2015-1856? Yes. CVE-2015-1856 is fixed in 2.3.0. Upgrade to this version or later.
Is CVE-2015-1856 exploitable, and should I be worried? Whether CVE-2015-1856 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2015-1856 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2015-1856? Upgrade swift to 2.3.0 or later.

Other vulnerabilities in swift

CVE-IDSeverityPackage summary

CVE-2026-49017Highswift: OpenStack Swift: s3api middleware enters an infinite loop when processing a truncated aws-chunked PUT request body CVE-2022-47950Mediumswift: OpenStack Swift XML external entities (XXE) Injection CVE-2013-4155Mediumswift: OpenStack Swift allows authenticated users to cause a denial of service CVE-2014-0006Highswift: OpenStack Swift Discloses Secret URLs to Timing Attack CVE-2014-3497Mediumswift: OpenStack Swift Cross-site Scriping vulnerability