How severe is CVE-2014-5356?

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

Which packages are affected by CVE-2014-5356?

CVE-2014-5356 affects the following packages: glance (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-5356?

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

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

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

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

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

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

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

CVE-2014-5356 was published on August 25, 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-5356 — glance

Fix: openstack/glance@12f43cf

CVE-2014-5356 is a CWE-264 vulnerability in glance. A fix is available for glance — see the affected versions and patch details below.

OpenStack Glance improper validation of the image_size_cap configuration option

Also known asGHSA-479j-jf2p-38pgPYSEC-2026-810

Published

Aug 25, 2014

Updated

Jul 7, 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 ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍glance

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 Image Registry and Delivery Service (Glance) before 2013.2.4, 2014.x before 2014.1.3, and Juno before Juno-3, when using the V2 API, does not properly enforce the image_size_cap configuration option, which allows remote authenticated users to cause a denial of service (disk consumption) by uploading a large image.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`glance`	all versions	11.0.0a0`pip install --upgrade 'glance==11.0.0a0'`

Affected Products

2 products · 10 configurations

ubuntu linuxcanonical

1 version

14.04

Application

image registry and delivery service \(glance\)openstack

≤ 2013.2.3

8 versions

2013.22013.2.12013.2.22014.12014.1.12014.1.2juno-1juno-2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update glance to 11.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-5356 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
OpenStack 4 for RHEL 6	`openstack-glance-0:2013.2.4-1.el6ost`	RHSA-2014:1685
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-glance-0:2014.1.2-5.el6ost`	RHSA-2014:1338
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-glance-0:2014.1.2-3.el7ost`	RHSA-2014:1337

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-5356 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works