Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

OpenStack Glance is vulnerable to Exposure of Sensitive Information

CVE-2013-1840GHSA-c8w9-83vg-r8vv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (glance 11.0.0a0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI glance

    Affected
    < 11.0.0a0
    Fixed in
    11.0.0a0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2013-1840: 1.72% estimated exploitation activity in the next 30 days; percentile 77.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 operator's backend credentials via a request for a cached image.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-c8w9-83vg-r8vv

  2. Revision 1 · created ·

    Published from osv record GHSA-c8w9-83vg-r8vv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-1840

Advisory: OpenStack Glance is vulnerable to Exposure of Sensitive Information
IDs: CVE-2013-1840, GHSA-c8w9-83vg-r8vv
Record: https://patchnext.com/advisories/cve-2013-1840 (revision 2, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: glance 11.0.0a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI glance: affected < 11.0.0a0; fixed in 11.0.0a0

## Suggested inspection (read-only)
- `python -m pip show glance`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on glance.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c8w9-83vg-r8vv (OSV record GHSA-c8w9-83vg-r8vv lists affected ranges: PyPI glance >=0 <11.0.0a0 (fixed))
- Verified: https://github.com/advisories/GHSA-c8w9-83vg-r8vv (GitHub-reviewed advisory GHSA-c8w9-83vg-r8vv lists affected ranges: PyPI glance >=0 <11.0.0a0)

Commands are suggestions: review each one before running it.

Loading voting…