CVE-2025-49574 json
Quarkus potential data leak when duplicating a duplicated context
published last yr. modified last mo. also EUVD-2025-18925 , GHSA-9623-mj7j-p9v4
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven io.quarkus:quarkus-vertx 3.15.6, 3.20.2, 3.24.1
- quarkus quarkus 3.15.6, 3.20.2, 3.24.1
- io.quarkus quarkus-vertx 3.15.6, 3.20.2, 3.24.1
Is CVE-2025-49574 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-49574 updated cvss 6.4
io.quarkus/quarkus-vertx: Quarkus potential data leak
-
Red Hat Cryostat 4 quarkus-vertx Red Hat OpenShift Serverless openshift-serverless-1/kn-ekb-receiver-rhel8, openshift-serverless-1/kn-ekb-dispatcher-rhel8, openshift-serverless-1/kn-ekb-post-install-rhel8, openshift-serverless-1/kn-ekb-webhook-kafka-rhel8, openshift-serverless-1/kn-ekb-kafka-controller-rhel8, openshift-serverless-1/kn-eventing-istio-controller-rhel8, +9 more Red Hat build of Apache Camel - HawtIO 4 quarkus-vertx Red Hat build of Apache Camel 4 for Quarkus 3 quarkus-cxf-bom, quarkus-camel-bom Red Hat build of Apicurio Registry 2 quarkus-vertx Red Hat build of Apicurio Registry 3 quarkus-vertxaffected: workaround, no fix available “Fix deferred”
+12 more productsfewer
Red Hat build of Debezium 2 quarkus-vertx Red Hat build of Debezium 3 quarkus-vertx Red Hat build of OptaPlanner 8 quarkus-vertx Red Hat Data Grid 8 quarkus-vertx Red Hat Fuse 7 quarkus-vertx Red Hat Integration Camel K 1 quarkus-vertx Red Hat JBoss Enterprise Application Platform 8 quarkus-vertx Red Hat JBoss Enterprise Application Platform Expansion Pack quarkus-vertx Red Hat OpenShift AI (RHOAI) rhoai/odh-dashboard-rhel9, rhoai/odh-trustyai-service-rhel8, rhoai/odh-trustyai-service-rhel9 Red Hat Process Automation 7 quarkus-vertx Red Hat streams for Apache Kafka quarkus-vertx Red Hat streams for Apache Kafka 2 quarkus-vertx -
Red Hat build of Quarkus 3.15.6fixed: vendor fix RHSA-2025:13012
-
Red Hat build of Quarkus 3.20.2.redhat quarkus-vertx 3.20.2.redhat-00003fixed: vendor fix RHSA-2025:13010
-
Red Hat Streams for Apache Kafka 3.0.0fixed: vendor fix RHSA-2025:12511
-
Red Hat Streams for Apache Kafka 3.1.0fixed: vendor fix RHSA-2025:23417
-
Red Hat build of Quarkus 3.20.2.redhat jna 5.8.0, lit 3.2.1, bson 5.3.1, db2 1.20.6, h2 2.3.230, y18n 5.0.8, +1017 morenot affected: vulnerable code not present
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.4 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.quarkus:quarkus-vertx | <3.15.6 >=3.16.0.CR1, <3.20.2 >=3.21.0.CR1, <3.24.1 |
3.15.6 3.20.2 3.24.1 |
Affected products
- quarkusio quarkus
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
github.com
/quarkusio/quarkus/pull/48486
web
-
github.com
/quarkusio/quarkus/commit/2b58f59f4bf0bae7d35b1abb585b65f2a66787d1
web
-
github.com
/quarkusio/quarkus/commit/31e8a3bfcf4e223788615d5ce25eb929ca251275
web
-
github.com
/quarkusio/quarkus/commit/d1ee57e7b826872b6355cfec0ae13465840e232c
web
-
github.com
/quarkusio/quarkus/security/advisories/GHSA-9623-mj7j-p9v4
web
-
github.com
/quarkusio/quarkus/issues/48227
web
-
github.com
/quarkusio/quarkus/releases/tag/3.24.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-49574
advisory
-
github.com
/quarkusio/quarkus
package
Sources
- CVE List CVE-2025-49574
- GitHub Advisory GHSA-9623-mj7j-p9v4
- NVD CVE-2025-49574
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.