Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.0, there is a potential data leak when duplicating a duplicated context. Quarkus extensively uses the Vert.x duplicated context to implement context propagation. With the new semantic data from one transaction can leak to the data from another transaction. From a Vert.x point of view, this new semantic clarifies the behavior. A significant amount of data is stored in the duplicated context, including request scope, security details, and metadata. Duplicating a duplicated context is rather rare and is only done in a few places. This issue has been patched in version 3.24.0.
Metrics
Affected Vendors & Products
References
History
Tue, 24 Jun 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Tue, 24 Jun 2025 00:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
threat_severity
|
Mon, 23 Jun 2025 20:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.0, there is a potential data leak when duplicating a duplicated context. Quarkus extensively uses the Vert.x duplicated context to implement context propagation. With the new semantic data from one transaction can leak to the data from another transaction. From a Vert.x point of view, this new semantic clarifies the behavior. A significant amount of data is stored in the duplicated context, including request scope, security details, and metadata. Duplicating a duplicated context is rather rare and is only done in a few places. This issue has been patched in version 3.24.0. | |
Title | Quarkus potential data leak when duplicating a duplicated context | |
Weaknesses | CWE-668 | |
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-06-23T19:47:05.454Z
Updated: 2025-06-24T13:33:07.194Z
Reserved: 2025-06-06T15:44:21.555Z
Link: CVE-2025-49574

Updated: 2025-06-24T13:33:03.488Z

Status : Awaiting Analysis
Published: 2025-06-23T20:15:28.170
Modified: 2025-06-23T20:16:21.633
Link: CVE-2025-49574
