CVE-2023-6393 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in io.quarkus:quarkus-cache. A fix is available for io.quarkus:quarkus-cache — see the affected versions and patch details below.
Quarkus Cache Runtime exposes sensitive information to an unauthorized actor
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.quarkus:quarkus-cache☕io.quarkus:quarkus-cacheReal-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
A flaw was found in the Quarkus Cache Runtime. When request processing utilizes a Uni cached using @CacheResult and the cached Uni reuses the initial "completion" context, the processing switches to the cached Uni instead of the request context. This is a problem if the cached Uni context contains sensitive information, and could allow a malicious user to benefit from a POST request returning the response that is meant for another user, gaining access to sensitive data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-cache | ≥ 3.3.0.CR1&&< 3.5.2 | 3.5.2io.quarkus:quarkus-cache:3.5.2 |
| ☕Maven | io.quarkus:quarkus-cache | ≥ 3.2.0.CR1&&< 3.2.9.Final | 3.2.9.Finalio.quarkus:quarkus-cache:3.2.9.Final |
Affected Products
build of quarkusredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-cache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-cache to 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6393 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat rates this as a Moderate impact due to the difficulty and randomness that is required to successfully exploit this vulnerability.
No mitigation is currently available for this flaw.Source: Red Hat security advisory for CVE-2023-6393 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2023-6393 in your dependencies?
Find it across Maven, including transitive dependencies.