OpenStack Octavia Fixes HAProxy Configuration Injection
Tech GuruQuick Answer
The authority published OSSA-2026-039 for OpenStack Octavia deployments using the Amphora provider driver. OpenStack reclassified control-character validation flaws after a proof of concept demonstrated root command execution on the provider-managed amphora, cross-tenant secret exposure, and control-plane reachability. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory OpenStack Octavia deployments using the Amphora provider driver, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | OpenStack Octavia deployments using the Amphora provider driver |
|---|---|
| Advisory | OSSA-2026-039 |
| CVEs | CVE-2026-94571, CVE-2026-94572 |
| Authoritative release date | 2026-09-21 20:09:16.848 UTC |
| Authority revision date | 2026-09-21 22:23:28 UTC |
| Affected versions | Octavia 0.8.0 through versions before 16.1.0, plus 17.0.0 and 18.0.0; only the Amphora provider is affected. |
| Fixed version | Octavia 16.1.0, 17.0.1, or 18.0.1 with both branch-specific fixes applied |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
OpenStack reclassified control-character validation flaws after a proof of concept demonstrated root command execution on the provider-managed amphora, cross-tenant secret exposure, and control-plane reachability.
What To Validate Now
- Inventory. Locate OpenStack Octavia deployments using the Amphora provider driver deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Octavia 0.8.0 through versions before 16.1.0, plus 17.0.0 and 18.0.0; only the Amphora provider is affected. Do not infer applicability from product family or severity alone.
- Remediate. Apply Octavia 16.1.0, 17.0.1, or 18.0.1 with both branch-specific fixes applied through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
