Glance vulnerabilitiesRanked by how likely they are to be used.

Product86 versions
The short answer

Glance is made by Openstack. We track 11 published vulnerabilities in it, across 86 versions. None of them is on the list of flaws known to be exploited today. If you run Glance, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Glance vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Glance's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Glance flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 3.1%

    The image parser in OpenStack Cinder 7.0.2 and 8.0.0 through 8.1.1; Glance before 11.0.1 and 12.0.0; and Nova before 12.0.4 and 13.0.0 does not properly limit qemu-img calls, which might allow attackers to cause a...

    CVSS7.5Published7 Oct 2016
  2. 3.1%

    OpenStack Image Registry and Delivery Service (Glance) Folsom, Grizzly before 2013.1.4, and Havana before 2013.2, when the download_image policy is configured, does not properly restrict access to cached images,...

    CVSS3.5Published27 Oct 2013
  3. 2.3%

    A vulnerability was found in Openstack Glance.

    CVSS6.5Published31 Jul 2018
  4. 2.1%

    An SSRF issue was discovered in OpenStack Glance before Newton.

    CVSS5.8Published21 Mar 2017
  5. 1.5%

    The import task action in OpenStack Image Service (Glance) 2015.1.x before 2015.1.2 (kilo), when using the V2 API, allows remote authenticated users to read arbitrary files via a crafted backing file for a qcow2 image.

    CVSS3.5Published19 Aug 2015
  6. 1.4%

    The v1 API in OpenStack Glance Essex (2012.1), Folsom (2012.2), and Grizzly, when using the single-tenant Swift or S3 store, reports the location field, which allows remote authenticated users to obtain the...

    CVSS3.5Published22 Mar 2013
  7. 1.3%

    OpenStack Glance before 2015.1.1 (kilo) allows remote authenticated users to cause a denial of service (disk consumption) by repeatedly using the import task flow API to create images and then deleting them.

    CVSS4.0Published14 Aug 2015
  8. 1.3%

    The image signature algorithm in OpenStack Glance 11.0.0 allows remote attackers to bypass the signature verification process via a crafted image, which triggers an MD5 collision.

    CVSS5.5Published29 Mar 2017
  9. 1.0%

    An issue was discovered in OpenStack Cinder before 19.1.2, 20.x before 20.0.2, and 21.0.0; Glance before 23.0.1, 24.x before 24.1.1, and 25.0.0; and Nova before 24.1.2, 25.x before 25.0.2, and 26.0.0.

    CVSS5.7Published26 Jan 2023
  10. 0.8%

    An issue was discovered in OpenStack Cinder through 24.0.0, Glance before 28.0.2, and Nova before 29.0.3.

    CVSS6.5Published5 Jul 2024
Precursor Intelligence

Running Glance? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 11 published vulnerabilities listed under the name Glance, across 86 versions.

None of Glance's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Glance. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.