GHSA-f4g4-cj8f-3cr9 CVE-2017-7214 PYSEC-2026-432

OpenStack Nova logs sensitive context from notification exceptions

Critical PyPI

Severity: 9.8 / 10; Critical · CVSS 3.0
Exploit chance (EPSS): 2.30%; Chance of exploitation in the next 30 days. Higher than 83.31% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-532 Insertion of Sensitive Information into Log File
Fix: 13.1.4; Upgrade nova to this version or later

Description

An issue was discovered in exception_wrapper.py in OpenStack Nova 13.x through 13.1.3, 14.x through 14.0.4, and 15.x through 15.0.1. Legacy notification exception contexts appearing in ERROR level logs may include sensitive information such as account passwords and authorization tokens.

Affected versions

PyPI

Package	Vulnerable	Fixed in
nova	`>= 13.0.0, < 13.1.4`	`13.1.4`
nova	`>= 14.0.0, < 14.0.5`	`14.0.5`
nova	`>= 15.0.1, < 15.0.2`	`15.0.2`
nova	`>= 13.0.0, < 13.1.4` `>= 14.0.0, < 14.0.5` `>= 15.0.1, < 15.0.2`	`13.1.4` `14.0.5` `15.0.2`

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 → `13.1.4`

pip

pip install --upgrade "nova>=13.1.4"

poetry

poetry add "nova>=13.1.4"

uv

uv add "nova>=13.1.4"

Severity breakdown

CVSS 3.0 9.8

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

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

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it

Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution: Remove debug log files before deploying the application into production.
Operation: Protect log files against unauthorized read/write.
Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Advisories

Packages

Timeline

May 14, 2022 Published
Jul 2, 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-22jm-4hxw-35jf OpenStack Nova can leak consoleauth token into log files	Low	Also affects nova
GHSA-43cm-73px-5v4m OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors	Low	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