# CVE-2026-42333: quarkus-openapi-generator has overly broad path-parameter matching that sends authentication headers to unintended operations

> Overly broad path matching in Quarkus OpenAPI Generator leaks authentication credentials to unintended endpoints, exposing sensitive tokens to attackers.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-fr8f-rwjx-f32v

## What is CVE-2026-42333?

CVE-2026-42333 is a medium-severity vulnerability in quarkiverse quarkus-openapi-generator, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Quarkus OpenAPI Generator is Quarkus' extensions for generation of Rest Clients and server stubs generation. Prior to versions 2.11.1-lts, 2.16.0-lts, and 2.17.0, the generated authentication filter matches OpenAPI path templates too broadly when deciding whether to attach credentials. A security scheme configured for one operation can therefore be applied to a different same-method operation whose path only partially resembles the protected template, causing bearer tokens, API keys, or basic credentials to be sent to unintended endpoints. This issue has been patched in versions 2.11.1-lts, 2.16.0-lts, and 2.17.0.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

4 open source packages ship an affected version, including io.quarkiverse.openapi.generator:quarkus-openapi-generator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkiverse.openapi.generator:quarkus-openapi-generator` | Maven | All versions | 2.16.0-lts |
| `io.quarkiverse.openapi.generator:quarkus-openapi-generator` | Maven | All versions | 2.16.0-lts |
| `io.quarkiverse.openapi.generator:quarkus-openapi-generator` | Maven | From 2.16.0 | 2.17.0 |
| `io.quarkiverse.openapi.generator:quarkus-openapi-generator` | Maven | From 2.16.0 | 2.17.0 |

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

Upgrade io.quarkiverse.openapi.generator:quarkus-openapi-generator to a fixed version for your release line: 2.16.0-lts or 2.17.0.

## Is CVE-2026-42333 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42333 is a medium-severity vulnerability in quarkiverse quarkus-openapi-generator, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42333 exists.

Affected packages and fixed versions:
- io.quarkiverse.openapi.generator:quarkus-openapi-generator (Maven): affected all versions; fixed in 2.16.0-lts
- io.quarkiverse.openapi.generator:quarkus-openapi-generator (Maven): affected all versions; fixed in 2.16.0-lts
- io.quarkiverse.openapi.generator:quarkus-openapi-generator (Maven): affected from 2.16.0; fixed in 2.17.0
- io.quarkiverse.openapi.generator:quarkus-openapi-generator (Maven): affected from 2.16.0; fixed in 2.17.0

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-42333/ (Markdown: https://insights.sbomify.com/CVE-2026-42333/index.md)
```

## Sources

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

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