How severe is CVE-2019-17134?

CVE-2019-17134 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-17134?

CVE-2019-17134 affects the following packages: octavia (PyPI), octavia (PyPI), octavia (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-17134?

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

How do I detect CVE-2019-17134 in my PyPI dependencies?

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.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2019-17134 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-17134, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-17134?

CVE-2019-17134 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th 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-2019-17134?

CVE-2019-17134 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-17134 published, and has it been updated?

CVE-2019-17134 was published on October 8, 2019 and was last updated on October 24, 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

CRITICAL severity

CVE-2019-17134 — octavia

CRITICALFix: openstack/octavia@1725517

CVE-2019-17134 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in octavia. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for octavia — see the affected versions and patch details below.

OpenStack Octavia Amphora-Agent not requiring Client-Certificate

Also known asGHSA-r4v4-3jj7-jc29PYSEC-2026-433

Published

Oct 8, 2019

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% 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

3 pkgs affected

🐍octavia🐍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

Amphora Images in OpenStack Octavia >=0.10.0 <2.1.2, >=3.0.0 <3.2.0, >=4.0.0 <4.1.0 allows anyone with access to the management network to bypass client-certificate based authentication and retrieve information or issue configuration commands via simple HTTP requests to the Agent on port https/9443, because the cmd/agent.py gunicorn cert_reqs option is True but is supposed to be ssl.CERT_REQUIRED.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`octavia`	≥ 0.10.0&&< 2.1.2	2.1.2`pip install --upgrade 'octavia==2.1.2'`
🐍PyPI	`octavia`	≥ 3.0.0&&< 3.2.0	3.2.0`pip install --upgrade 'octavia==3.2.0'`
🐍PyPI	`octavia`	≥ 4.0.0&&< 4.1.0	4.1.0`pip install --upgrade 'octavia==4.1.0'`

Affected Products

2 products · 4 configurations

ubuntu linuxcanonical

1 version

19.04

Application

octaviaopendev

≥ 4.0.0 && < 4.1.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Amphora Images in OpenStack Octavia >=0.10.0 <2.1.2, >=3.0.0 <3.2.0, >=4…

storyboard.openstack.orgNVDNov 2019

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update octavia to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17134 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

Workaround published by Red Hat

There is no mitigation for this issue, the flaw can only be resolved by applying updates.

Source: Red Hat security advisory for CVE-2019-17134 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenStack Platform 13.0 (Queens)	`openstack-octavia-0:2.1.2-1.el7ost`	RHSA-2019:3788
Red Hat OpenStack Platform 14.0 (Rocky)	`openstack-octavia-0:3.1.0-3.el7ost`	RHSA-2019:3743
Red Hat OpenStack Platform 15.0 (Stein)	`openstack-octavia-0:4.1.2-0.20200114080449.5a71643.el8ost`	RHSA-2020:0721

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-17134 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works