CVE-2025-49574
Quarkus potential data leak when duplicating a duplicated context
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.1, 3.20.2, and 3.15.6, 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.1, 3.20.2, and 3.15.6.
Attack profile
How easy it is to exploit
- Attack vector
- Adjacent network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
Quarkus potential data leak when duplicating a duplicated context
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.1, 3.20.2, and 3.15.6, 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.1, 3.20.2, and 3.15.6.
- Record
CVE-2025-49574- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-668
- Updated
- 2026-11-02
EUVDEUVD-2025-18925
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.1, 3.20.2, and 3.15.6, 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.1, 3.20.2, and 3.15.6.
- Record
EUVD-2025-18925- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-9623-mj7j-p9v4
Quarkus potentially leaks data when duplicating a duplicated context
Impact
Vert.x 4.5.12 has changed the semantics of the duplication of duplicated context.
Duplicated context is an object used to propagate data through a processing (synchronous or asynchronous). Each "transaction" or "processing" runs on its own isolated duplicated context.
Initially, duplicating a duplicated context was creating a fresh (empty) new context, meaning that the new duplicated context can be used to managed a separated transaction.
In Vert.x 4.5.12, this semantics has changed, and since the content of the parent duplicated context is copied into the new one, potentially leaking data.
This CVE is especially for Quarkus as 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:
- Quarkus REST Client when using OTel (but it's the same transaction, so no leak)
- Quarkus Messaging connectors
- Quarkus SmallRye Health (same transaction, so no leak)
Patches
After discussion with the Vert.x team, the change will be rolled back in Vert.x 4.x. A new API will be added to Vert.x 5 do distinguish the 2 cases.
Workarounds
When duplicating a duplicated context, the following code can be done to avoid the potential leak:
((ContextInternal) VertxContext.getRootContext(ctx)).duplicate()
This workaround would not be required once the Vert.x version containing the fix will be included. Note that the workaround would still work.
References
This issue have been reported in https://github.com/quarkusio/quarkus/issues/48227.
- Record
GHSA-9623-mj7j-p9v4- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-668
- Updated
- 2026-11-02
NVD
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.1, 3.20.2, and 3.15.6, 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.1, 3.20.2, and 3.15.6.
- Record
CVE-2025-49574- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-668
- Updated
- 2026-11-02
OSV
Quarkus potential data leak when duplicating a duplicated context
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. In versions prior to 3.24.1, 3.20.2, and 3.15.6, 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.1, 3.20.2, and 3.15.6.
- Record
CVE-2025-49574- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-668
- Updated
- 2026-11-02
OSVGHSA-9623-mj7j-p9v4
Quarkus potentially leaks data when duplicating a duplicated context
Impact
Vert.x 4.5.12 has changed the semantics of the duplication of duplicated context.
Duplicated context is an object used to propagate data through a processing (synchronous or asynchronous). Each "transaction" or "processing" runs on its own isolated duplicated context.
Initially, duplicating a duplicated context was creating a fresh (empty) new context, meaning that the new duplicated context can be used to managed a separated transaction.
In Vert.x 4.5.12, this semantics has changed, and since the content of the parent duplicated context is copied into the new one, potentially leaking data.
This CVE is especially for Quarkus as 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:
- Quarkus REST Client when using OTel (but it's the same transaction, so no leak)
- Quarkus Messaging connectors
- Quarkus SmallRye Health (same transaction, so no leak)
Patches
After discussion with the Vert.x team, the change will be rolled back in Vert.x 4.x. A new API will be added to Vert.x 5 do distinguish the 2 cases.
Workarounds
When duplicating a duplicated context, the following code can be done to avoid the potential leak:
((ContextInternal) VertxContext.getRootContext(ctx)).duplicate()
This workaround would not be required once the Vert.x version containing the fix will be included. Note that the workaround would still work.
References
This issue have been reported in https://github.com/quarkusio/quarkus/issues/48227.
- Record
GHSA-9623-mj7j-p9v4- CVSS 3.1
- 6.4 Medium
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-668
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
io.quarkus:quarkus-vertxMaven |
through 3.15.5 | 3.15.6 |
io.quarkus:quarkus-vertxMaven |
3.16.0.CR1 to 3.20.1 | 3.20.2 |
io.quarkus:quarkus-vertxMaven |
3.21.0.CR1 to 3.24.0 | 3.24.1 |
io.quarkus:quarkus-vertxMaven |
before 3.15.6, plus listed versions 0.11.00.12.00.13.00.13.10.13.2 Show 45 moreShow less0.13.30.14.00.15.00.16.00.16.10.17.00.18.00.19.00.19.10.20.00.21.00.21.10.21.20.22.00.23.00.23.10.23.20.24.00.25.00.26.00.26.10.27.00.28.00.28.11.0.0.CR11.0.0.CR21.0.0.Final1.0.1.Final1.1.0.CR11.1.0.Final1.1.1.Final1.10.0.CR11.10.0.Final1.10.1.Final1.10.2.Final1.10.3.Final1.10.4.Final1.10.5.Final1.11.0.Beta11.11.0.Beta21.11.0.CR11.11.0.Final1.11.1.Final1.11.2.Final1.11.3.Final |
3.15.6 |
io.quarkus:quarkus-vertxMaven |
3.16.0.CR1 up to 3.20.2, plus listed versions 3.16.03.16.13.16.23.16.33.16.4 Show 25 moreShow less3.17.03.17.0.CR13.17.13.17.23.17.33.17.43.17.53.17.63.17.73.17.83.18.03.18.0.CR13.18.13.18.23.18.33.18.43.19.03.19.0.CR13.19.13.19.23.19.33.19.43.20.03.20.0.CR13.20.1 |
3.20.2 |
io.quarkus:quarkus-vertxMaven |
3.21.0.CR1 up to 3.24.1, plus listed versions 3.21.03.21.13.21.23.21.33.21.4 Show 13 moreShow less3.22.03.22.0.CR13.22.13.22.23.22.33.23.03.23.0.CR13.23.13.23.23.23.33.23.43.24.03.24.0.CR1 |
3.24.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-49574 is a medium vulnerability (CVSS 6.4) in Quarkusio Quarkus, published June 23, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.28%, the 20th percentile. Fixed in io.quarkus:quarkus-vertx 3.15.6.
References
github.com/quarkusio/quarkus/security/advisories/GHSA-9623-mj7j-p9v4
Left out here: 283 versions. The JSON record has them.