CVE-2026-42333
CVE-2026-42333 is a Information Exposure vulnerability in io.quarkiverse.openapi.generator:quarkus-openapi-generator. O3 Security confirms whether CVE-2026-42333 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
quarkus-openapi-generator has overly broad path-parameter matching that sends authentication headers to unintended operations
Blast Radius
io.quarkiverse.openapi.generator:quarkus-openapi-generator☕io.quarkiverse.openapi.generator:quarkus-openapi-generatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkiverse.openapi.generator:quarkus-openapi-generator | all versions | 2.16.0-lts |
| ☕Maven | io.quarkiverse.openapi.generator:quarkus-openapi-generator | ≥ 2.16.0&&< 2.17.0 | 2.17.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkiverse.openapi.generator:quarkus-openapi-generator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.quarkiverse.openapi.generator:quarkus-openapi-generator to 2.16.0-lts or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42333 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-42333 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-42333. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-42333 in your dependencies?
O3 detects CVE-2026-42333 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.