GHSA-22jm-4hxw-35jf CVE-2015-9543 PYSEC-2026-857

OpenStack Nova can leak consoleauth token into log files

Low PyPI

Severity: 3.3 / 10; Low · CVSS 3.1
Exploit chance (EPSS): 0.41%; Chance of exploitation in the next 30 days. Higher than 35.33% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix: 18.2.4; Upgrade nova to this version or later

Description

An issue was discovered in OpenStack Nova before 18.2.4, 19.x before 19.1.0, and 20.x before 20.1.0. It can leak consoleauth tokens into log files. An attacker with read access to the service's logs may obtain tokens used for console access. All Nova setups using novncproxy are affected. This is related to NovaProxyRequestHandlerBase.new_websocket_client in console/websocketproxy.py.

Affected versions

PyPI

Package	Vulnerable	Fixed in
nova	`< 18.2.4`	`18.2.4`
nova	`>= 19.0.0, < 19.1.0`	`19.1.0`
nova	`>= 20.0.0, < 20.1.0`	`20.1.0`
nova	`< 18.2.4` `>= 19.0.0, < 19.1.0` `>= 20.0.0, < 20.1.0`	`18.2.4` `19.1.0` `20.1.0`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

nova PyPI → `18.2.4`

pip

pip install --upgrade "nova>=18.2.4"

poetry

poetry add "nova>=18.2.4"

uv

uv add "nova>=18.2.4"

Severity breakdown

CVSS 3.1 3.3

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it

Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

pypi.org/project/nova

Timeline

May 24, 2022 Published
Jul 7, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-mfg3-p6m3-gjgr OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints	High	Also affects nova
GHSA-m4f3-qp2w-gwh6 OpenStack Nova calls qemu-img without format restrictions for resize	High	Also affects nova
GHSA-rm86-h44c-2r2m OpenStack Nova vulnerable to unauthorized access to potentially sensitive data	Medium	Also affects nova
GHSA-r4v4-w9pv-6fph OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access	Medium	Also affects nova
GHSA-7h75-hwxx-qpgc OpenStack Cinder, glance, and Nova vulnerable to Path Traversal	Medium	Also affects nova
GHSA-v725-c588-h936 OpenStack Nova Changing vnic_type breaks compute service restart	Low	Also affects nova
GHSA-43cm-73px-5v4m OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors	Low	Also affects nova
GHSA-j6xh-q826-55jw OpenStack Compute (Nova) vulnerable to denial of service via XML Entity Expansion attack	Medium	Also affects nova

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor