How severe is GHSA-j4mh-9wq6-8rg6?

No CVSS score has been assigned to GHSA-j4mh-9wq6-8rg6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j4mh-9wq6-8rg6?

GHSA-j4mh-9wq6-8rg6 affects the following packages: glance (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-j4mh-9wq6-8rg6?

Update glance to 11.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j4mh-9wq6-8rg6 is resolved across your whole dependency graph.

How do I detect GHSA-j4mh-9wq6-8rg6 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j4mh-9wq6-8rg6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j4mh-9wq6-8rg6?

O3 pinpoints whether GHSA-j4mh-9wq6-8rg6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j4mh-9wq6-8rg6 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-j4mh-9wq6-8rg6, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-j4mh-9wq6-8rg6?

GHSA-j4mh-9wq6-8rg6 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j4mh-9wq6-8rg6 published, and has it been updated?

GHSA-j4mh-9wq6-8rg6 was published on May 17, 2022 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

GHSA-j4mh-9wq6-8rg6

GHSA-j4mh-9wq6-8rg6 is a CWE-399 vulnerability in glance. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-j4mh-9wq6-8rg6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenStack Glance Bypass the storage quota and Denial of service

Also known asCVE-2014-9623PYSEC-2026-813

Published

May 17, 2022

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

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 Glance 2014.2.x through 2014.2.1, 2014.1.3, and earlier allows remote authenticated users to bypass the storage quota and cause a denial of service (disk consumption) by deleting an image in the saving state.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`glance`	all versions	11.0.0a0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenStack Glance 2014.2.x through 2014.2.1, 2014.1.3, and earlier allows…

bugs.launchpad.netNVDDec 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glance. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update glance to 11.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j4mh-9wq6-8rg6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j4mh-9wq6-8rg6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j4mh-9wq6-8rg6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-j4mh-9wq6-8rg6 in your dependencies?

O3 detects GHSA-j4mh-9wq6-8rg6 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works