What is CVE-2026-34881?

CVE-2026-34881 is a medium-severity server-side request forgery (SSRF) vulnerability in glance (pip), affecting versions < 29.2.0. It is fixed in 29.2.0, 30.2.0, 31.1.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-34881?

CVE-2026-34881 has a CVSS score of 5.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of glance are affected by CVE-2026-34881?

glance (pip) versions < 29.2.0 is affected.

Is there a fix for CVE-2026-34881?

Yes. CVE-2026-34881 is fixed in 29.2.0, 30.2.0, 31.1.0. Upgrade to this version or later.

Is CVE-2026-34881 exploitable, and should I be worried?

Whether CVE-2026-34881 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-2026-34881 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.

CVE-2026-34881 in glance | Intelligent Application Security

Q: How severe is CVE-2026-34881?

CVE-2026-34881 has a CVSS score of 5.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of glance are affected by CVE-2026-34881?

glance (pip) versions < 29.2.0 is affected.

Q: Is there a fix for CVE-2026-34881?

Yes. CVE-2026-34881 is fixed in 29.2.0, 30.2.0, 31.1.0. Upgrade to this version or later.

Q: Is CVE-2026-34881 exploitable, and should I be worried?

Whether CVE-2026-34881 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-2026-34881 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-2026-34881?

Upgrade: glance to 29.2.0 or later, glance to 30.2.0 or later, glance to 31.1.0 or later.

Summary

OpenStack Glance versions < 29.1.1, >= 30.0.0 < 30.1.1, == 31.0.0 are affected by Server-Side Request Forgery (SSRF). By use of HTTP redirects, an authenticated user can bypass URL validation checks and redirect to internal services. Only the glance image import functionality is affected. In particular, the web-download and glance-download import methods are subject to this vulnerability, as is the optional (not enabled by default) ovf_process image import plugin.

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-34881 has a CVSS score of 5.0 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (29.2.0, 30.2.0, 31.1.0); upgrading removes the vulnerable code path.

Affected versions

glance (< 29.2.0) glance (>= 30.0.0, < 30.2.0) glance (= 31.0.0)

Security releases

glance → 29.2.0 (pip) glance → 30.2.0 (pip) glance → 31.1.0 (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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

glance to 29.2.0 or later; glance to 30.2.0 or later; glance to 31.1.0 or later

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

Frequently Asked Questions

What is CVE-2026-34881? CVE-2026-34881 is a medium-severity server-side request forgery (SSRF) vulnerability in glance (pip), affecting versions < 29.2.0. It is fixed in 29.2.0, 30.2.0, 31.1.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
How severe is CVE-2026-34881? CVE-2026-34881 has a CVSS score of 5.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of glance are affected by CVE-2026-34881? glance (pip) versions < 29.2.0 is affected.
Is there a fix for CVE-2026-34881? Yes. CVE-2026-34881 is fixed in 29.2.0, 30.2.0, 31.1.0. Upgrade to this version or later.
Is CVE-2026-34881 exploitable, and should I be worried? Whether CVE-2026-34881 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-2026-34881 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-2026-34881?
- Upgrade glance to 29.2.0 or later
- Upgrade glance to 30.2.0 or later
- Upgrade glance to 31.1.0 or later

Other vulnerabilities in glance

CVE-2024-32498 CVE-2022-4134 CVE-2022-25937 CVE-2022-47951 CVE-2014-1948