# CVE-2026-74248: Missing authorization in Octavia

> Authenticated users can prevent deletion of QoS policies by associating them with amphorae, impacting policy management in OpenStack Octavia.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-74248, GHSA-3gfv-q5hp-jpcf, UBUNTU-CVE-2026-74248

## What is CVE-2026-74248?

CVE-2026-74248 is a medium-severity missing authorization vulnerability in OpenStack Octavia, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Octavia through 18.0.0 mishandles quality of service (QoS) policy authorization. By associating another project's QoS policy with an amphora, an authenticated user may prevent deletion of that policy. All Octavia deployments are affected.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-74248?


## How do I fix CVE-2026-74248?

Apply the vendor's patch.

## Is CVE-2026-74248 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74248 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74248 and fix it if it is affected.

What it is: CVE-2026-74248 is a medium-severity missing authorization vulnerability in OpenStack Octavia, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74248 exists.

Affected product: OpenStack Octavia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74248/ (Markdown: https://insights.sbomify.com/CVE-2026-74248/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74248
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74248
- OSV: https://osv.dev/vulnerability/CVE-2026-74248

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74248/
Summaries are generated and may contain mistakes; the official description above is the record.