Quarkus potentially leaks data when duplicating a duplicated context

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.4 · CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2025-49574: 0.28% estimated exploitation activity in the next 30 days; percentile 20.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

23 Jun 2025, 18:53 UTC

Last modified by the source

22 Dec 2025, 18:38 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9623-mj7j-p9v4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-49574

Advisory: Quarkus potentially leaks data when duplicating a duplicated context
IDs: CVE-2025-49574, GHSA-9623-mj7j-p9v4
Record: https://patchnext.com/advisories/cve-2025-49574 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.quarkus:quarkus-vertx 3.24.1, 3.20.2, 3.15.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.quarkus:quarkus-vertx: affected <= 3.15.5; >= 3.16.0.CR1, <= 3.20.1; >= 3.21.0.CR1, <= 3.24.0; fixed in 3.24.1, 3.20.2, 3.15.6

## Suggested inspection (read-only)
- Maven io.quarkus:quarkus-vertx: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.quarkus:quarkus-vertx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9623-mj7j-p9v4 (GitHub-reviewed advisory GHSA-9623-mj7j-p9v4 lists affected ranges: Maven io.quarkus:quarkus-vertx >=0 =3.16.0.CR1 =3.21.0.CR1 <=3.24.0)

Commands are suggestions: review each one before running it.