OpenStack Octavia up to 16.0.x/17.0.0/18.0.0 Amphora provider driver tls_ciphers injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 1.25+ |
Summary
A vulnerability has been found in OpenStack Octavia up to 16.0.x/17.0.0/18.0.0 and classified as very critical. This vulnerability affects unknown code of the component Amphora provider driver. The manipulation of the argument tls_ciphers leads to injection. This vulnerability is uniquely identified as CVE-2026-94572. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability was found in OpenStack Octavia up to 16.0.x/17.0.0/18.0.0. It has been rated as very critical. This issue affects an unknown part of the component Amphora provider driver. The manipulation of the argument tls_ciphers with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In OpenStack Octavia before 18.0.1, the Amphora provider driver did not validate the listener and pool tls_ciphers field for control characters. The value is written verbatim into the HAProxy configuration generated on the amphora, and thus an authenticated project member who owns a TLS-enabled load balancer can embed a newline and inject arbitrary HAProxy configuration directives. Only deployments using the Amphora provider are affected.
The advisory is shared at bugs.launchpad.net. The identification of this vulnerability is CVE-2026-94572 since 09/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/21/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.
Upgrading to version 16.1.0, 17.0.1 or 18.0.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.openstack.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Octavia 16.1.0/17.0.1/18.0.1
Timeline
09/21/2026 Advisory disclosed09/21/2026 CVE reserved
09/21/2026 VulDB entry created
09/21/2026 VulDB entry last update
Sources
Vendor: openstack.orgAdvisory: bugs.launchpad.net
Status: Confirmed
CVE: CVE-2026-94572 (🔒)
GCVE (CVE): GCVE-0-2026-94572
GCVE (VulDB): GCVE-100-408257
Entry
Created: 09/21/2026 22:37Changes: 09/21/2026 22:37 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.