Skip to content
Fencer Vulns
medium 5.3

CVE-2023-6393 json

Quarkus: potential invalid reuse of context when @cacheresult on a uni is used

published 2023-12-06 2 y ago modified 2026-09-29 41 d ago also GHSA-xfv5-jqgp-vqhj , EUVD-2023-3324

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.quarkus:quarkus-cache 3.2.9.Final, 3.5.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-6393 updated cvss 5.3

quarkus: Potential invalid reuse of context when @CacheResult on a Uni is used

  • Red Hat build of Quarkus quarkus-cache
    affected: workaround, no fix available “No mitigation is currently available for this flaw.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven io.quarkus:quarkus-cache
>=3.3.0.CR1, <3.5.2
>=3.2.0.CR1, <3.2.9.Final
3.5.2
3.2.9.Final

Affected products

  • Red Hat Red Hat build of Quarkus

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.