NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2018-16856 — octavia

HIGHFix: openstack/octavia@ae7c87f

CVE-2018-16856 is a high-severity (CVSS 7.5) CWE-532 vulnerability in octavia. A fix is available for octavia — see the affected versions and patch details below.

Openstack Octavia allows Insertion of Sensitive Information into Log File

Also known asPYSEC-2019-193
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.00%0.46%0.92%1.39%0.3%0.9%Apr 26Aug 26Oct 26

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

2 pkgs affected
🐍octavia🐍octavia

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

In a default Red Hat Openstack Platform Director installation, openstack-octavia before versions openstack-octavia 2.0.2-5 and openstack-octavia-3.0.1-0.20181009115732 creates log files that are readable by all users. Sensitive information such as private keys can appear in these log files allowing for information exposure.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIoctaviaall versions2.1.0pip install --upgrade 'octavia==2.1.0'
🐍PyPIoctavia≥ 3.0.0.0b1&&< 3.1.03.1.0pip install --upgrade 'octavia==3.1.0'

Affected Products

2 products · 5 configurations
Application
octaviaopenstack
≥ 3.0.0 && < 3.0.1-0.20181009115732
range
Application
openstackredhat
3 versions
121314

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update octavia to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16856 is resolved across your whole dependency graph.

  3. 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
ProductFixed inAdvisory
Red Hat OpenStack Platform 13.0 (Queens)openstack-octavia-0:2.0.3-2.el7ostRHSA-2019:0567
Red Hat OpenStack Platform 14.0 (Rocky)openstack-octavia-0:3.0.2-0.20181219195054.ec4c88e.el7ostRHSA-2019:0593

Frequently Asked Questions

In a default Red Hat Openstack Platform Director installation, openstack-octavia before versions openstack-octavia 2.0.2-5 and openstack-octavia-3.0.1-0.20181009115732 creates log files that are readable by all users. Sensitive information such as private keys can appear in these log files allowing for information exposure.
O3 Security · Impact-Aware SCA

Is CVE-2018-16856 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2018-16856: octavia Info Disclosure — Fixed in 2.1.0