What is CVE-2015-5286?

CVE-2015-5286 is a medium-severity uncontrolled resource consumption vulnerability in glance (pip), affecting versions < 2014.2.4. It is fixed in 2014.2.4, 2015.1.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which versions of glance are affected by CVE-2015-5286?

glance (pip) versions < 2014.2.4 is affected.

Is there a fix for CVE-2015-5286?

Yes. CVE-2015-5286 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.

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

Whether CVE-2015-5286 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-5286 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-5286?

Upgrade: glance to 2014.2.4 or later, glance to 2015.1.2 or later.

CVE-2015-5286 in glance

Q: Which versions of glance are affected by CVE-2015-5286?

glance (pip) versions < 2014.2.4 is affected.

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

Yes. CVE-2015-5286 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.

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

Whether CVE-2015-5286 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-5286 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-5286?

Upgrade: glance to 2014.2.4 or later, glance to 2015.1.2 or later.

Summary

OpenStack Image Service (Glance) allows remote authenticated users to bypass storage quota, cause denial of service

OpenStack Image Service (Glance) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) allows remote authenticated users to bypass the storage quota and cause a denial of service (disk consumption) by deleting images that are being uploaded using a token that expires during the process. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-9623.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

glance (< 2014.2.4) glance (>= 2015.1.0, < 2015.1.2)

Security releases

glance → 2014.2.4 (pip) glance → 2015.1.2 (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 the following packages to resolve this vulnerability:

glance to 2014.2.4 or later; glance to 2015.1.2 or later

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

Frequently Asked Questions

What is CVE-2015-5286? CVE-2015-5286 is a medium-severity uncontrolled resource consumption vulnerability in glance (pip), affecting versions < 2014.2.4. It is fixed in 2014.2.4, 2015.1.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which versions of glance are affected by CVE-2015-5286? glance (pip) versions < 2014.2.4 is affected.
Is there a fix for CVE-2015-5286? Yes. CVE-2015-5286 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.
Is CVE-2015-5286 exploitable, and should I be worried? Whether CVE-2015-5286 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-5286 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-5286?
- Upgrade glance to 2014.2.4 or later
- Upgrade glance to 2015.1.2 or later

Other vulnerabilities in glance

CVE-IDSeverityPackage summary

CVE-2026-34881Mediumglance: OpenStack Glance is affected by Server-Side Request Forgery (SSRF)CVE-2024-32498Highcinder: OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access CVE-2022-4134Lowglance: OpenStack Glance Inclusion of Functionality from Untrusted Control Sphere vulnerability CVE-2022-25937Mediumglance: Path traversal vulnerability in glance CVE-2022-47951Mediumcinder: OpenStack Cinder, glance, and Nova vulnerable to Path Traversal