CVE-2026-42333 — quarkus-openapi-generator
Fix: quarkiverse/quarkus-openapi-generator#1586CVE-2026-42333 is a Information Exposure vulnerability in io.quarkiverse.openapi.generator:quarkus-openapi-generator. A fix is available for io.quarkiverse.openapi.generator:quarkus-openapi-generator — see the affected versions and patch details below.
quarkus-openapi-generator has overly broad path-parameter matching that sends authentication headers to unintended operations
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42333.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
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-ltsio.quarkiverse.openapi.generator:quarkus-openapi-generator:2.16.0-lts |
| ☕Maven | io.quarkiverse.openapi.generator:quarkus-openapi-generator | ≥ 2.16.0&&< 2.17.0 | 2.17.0io.quarkiverse.openapi.generator:quarkus-openapi-generator: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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-42333 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2026-42333 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.