How severe is CVE-2021-4180?

CVE-2021-4180 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-4180?

CVE-2021-4180 affects the following packages: tripleo-heat-templates (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2021-4180?

Update tripleo-heat-templates to 11.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4180 is resolved across your whole dependency graph.

How do I detect CVE-2021-4180 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tripleo-heat-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-4180 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2021-4180 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-4180 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-4180?

CVE-2021-4180 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-4180?

CVE-2021-4180 is classified as Information Exposure (CWE-200), CWE-668 (CWE-668). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-4180 published, and has it been updated?

CVE-2021-4180 was published on March 24, 2022 and was last updated on July 6, 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

Not in CISA KEV

MEDIUM severity

CVE-2021-4180 — tripleo-heat-templates

MEDIUMFix: openstack/tripleo-heat-templates@160936d

CVE-2021-4180 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in tripleo-heat-templates. A fix is available for tripleo-heat-templates — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in OpenStack tripleo-heat-templates

Also known asPYSEC-2026-753

Published

Mar 24, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍tripleo-heat-templates

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

An information exposure flaw in openstack-tripleo-heat-templates allows an external user to discover the internal IP or hostname. An attacker could exploit this by checking the www_authenticate_uri parameter (which is visible to all end users) in configuration files. This would give sensitive information which may aid in additional system exploitation. A patch is available on the master branch and anticipated to be part of version 11.6.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tripleo-heat-templates`	all versions	11.6.1`pip install --upgrade 'tripleo-heat-templates==11.6.1'`

Affected Products

2 products · 4 configurations

Application

tripleo heat templatesopenstack

< 11.6.1

range

Application

openstackredhat

3 versions

1316.116.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tripleo-heat-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tripleo-heat-templates to 11.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4180 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat OpenStack Platform 16.1	`openstack-tripleo-heat-templates-0:11.3.2-1.20221013153262.el8ost`	RHSA-2022:8796
Red Hat OpenStack Platform 16.2	`openstack-tripleo-heat-templates-0:11.6.1-2.20220116004912.el8ost`	RHSA-2022:0995

Frequently Asked Questions

An information exposure flaw in openstack-tripleo-heat-templates allows an external user to discover the internal IP or hostname. An attacker could exploit this by checking the `www_authenticate_uri parameter` (which is visible to all end users) in configuration files. This would give sensitive information which may aid in additional system exploitation. A patch is available on the `master` branch and anticipated to be part of version 11.6.1.

O3 Security · Impact-Aware SCA

Is CVE-2021-4180 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure CWE-668CWE-668

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 24, 2022

Last updated

Jul 6, 2026

Identifiers

CVE-2021-4180

PYSEC-2026-753

References

Advisorynvd.nist.gov · CVE 2021 4180 Webgithub.com · 160936df134a471cfd245bd60964046027a571ea Webgithub.com · 2b9461e97fc5c4ceb0848d1cc4484f656bb85515 Webbugs.launchpad.net Webbugzilla.redhat.com · show bug.cgi Packagegithub.com · tripleo heat templates

Related vulnerabilities

Also affects tripleo-heat-templates

This CVE is medium severity; 3 of 3 other CVEs affecting tripleo-heat-templates are rated as high or higher (top: high).

CVE-2015-5271CVE-2015-5303CVE-2017-12155

Same weakness: CWE-200

This CVE is medium severity; 4 of 5 other CVEs with CWE-200 are rated as high or higher (top: high).

CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 6, 2026

CVE-2021-4180 — tripleo-heat-templates

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2021-4180 in your dependencies?