CVE-2025-49574: Quarkus vertx Quarkus Potentially Leaks Data When Vulnerability

MODERATE
Advisory Identifier: GHSA-9623-mj7j-p9v4
CVSS 6.4
CWE-668
Published
Advisory Summary

CVE-2025-49574 is a MODERATE (CVSS 6.4) quarkus potentially leaks data when vulnerability (CWE-668: Exposure of Resource to Wrong Sphere) affecting Quarkus vertx libraries in the Maven ecosystem. The issue involves quarkus potentially leaks data when duplicating a duplicated context. Remediation is available by upgrading affected packages to version 3.15.6, 3.20.2, 3.24.1.

CVE-2025-49574 at a Glance

CVE Identifier CVE-2025-49574
GHSA Identifier GHSA-9623-mj7j-p9v4
Severity MODERATE
CVSS v3.1 Base Score 6.4
CWE Classification CWE-668: Exposure of Resource to Wrong Sphere
Affected Product Quarkus vertx
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Adjacent (AV:A)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-49574

To remediate this vulnerability, upgrade all affected Quarkus vertx dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.quarkus:quarkus-vertx fixed: 3.15.6
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx</artifactId>
    <version>3.15.6</version>
</dependency>
io.quarkus:quarkus-vertx fixed: 3.20.2
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx</artifactId>
    <version>3.20.2</version>
</dependency>
io.quarkus:quarkus-vertx fixed: 3.24.1
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx</artifactId>
    <version>3.24.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.quarkus

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-49574, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.quarkus

Analyze the terminal output to locate any version of Quarkus vertx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.15.6), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.quarkus command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-668: Exposure of Resource to Wrong Sphere, where the product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. In Quarkus vertx, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: ```java ((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.

CVE-2025-49574 Affected Quarkus vertx Versions

3 component(s)
Fixed Versions:
3.15.63.20.23.24.1
Product / Package Ecosystem Affected Versions Fixed Version
io.quarkus:quarkus-vertx
Maven
< 3.15.6
3.15.6
io.quarkus:quarkus-vertx
Maven
≥ 3.16.0.CR1
< 3.20.2
3.20.2
io.quarkus:quarkus-vertx
Maven
≥ 3.21.0.CR1
< 3.24.1
3.24.1

References

Frequently Asked Questions

What is CVE-2025-49574?
CVE-2025-49574 is a security vulnerability in Quarkus vertx involving Quarkus potentially leaks data when duplicating a duplicated context under CWE-668: Exposure of Resource to Wrong Sphere.
Which Quarkus vertx versions are affected?
Affected versions include releases prior to 3.15.6, 3.20.2, 3.24.1 across affected packages: io.quarkus:quarkus-vertx.
What version fixes CVE-2025-49574?
Upgrading to 3.15.6, 3.20.2, 3.24.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is quarkus-vertx affected?
Yes, io.quarkus:quarkus-vertx is affected in releases prior to 3.15.6, 3.20.2, 3.24.1. Upgrade your dependency to 3.15.6, 3.20.2, 3.24.1 or later.
What is the CVSS score of CVE-2025-49574?
CVE-2025-49574 has a CVSS v3.1 base score of 6.4 (MODERATE) with vector string CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2025-49574?
CVE-2025-49574 is classified under CWE-668: Exposure of Resource to Wrong Sphere (The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.).
How can I check Maven dependencies for CVE-2025-49574?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.quarkus'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9623-mj7j-p9v4",
  "modified" : "2025-12-22T18:38:56Z",
  "published" : "2025-06-23T18:53:22Z",
  "aliases" : [ "CVE-2025-49574" ],
  "summary" : "Quarkus potentially leaks data when duplicating a duplicated context",
  "details" : "### Impact\n\nVert.x 4.5.12 has changed the semantics of the duplication of duplicated context.\n\nDuplicated 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.\n\nInitially, 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.\n\nIn 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. \n\nThis 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. \n\nA 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:\n\n- Quarkus REST Client when using OTel (but it's the same transaction, so no leak)\n- Quarkus Messaging connectors\n- Quarkus SmallRye Health (same transaction, so no leak)\n\n\n\n### Patches\n\nAfter 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.\n\n### Workarounds\n\nWhen duplicating a duplicated context, the following code can be done to avoid the potential leak:\n\n```java\n((ContextInternal) VertxContext.getRootContext(ctx)).duplicate()\n```\n\nThis workaround would not be required once the Vert.x version containing the fix will be included. Note that the workaround would still work. \n\n\n### References\n\nThis issue have been reported in https://github.com/quarkusio/quarkus/issues/48227.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.15.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.15.5"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.16.0.CR1"
      }, {
        "fixed" : "3.20.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.20.1"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.21.0.CR1"
      }, {
        "fixed" : "3.24.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.24.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/security/advisories/GHSA-9623-mj7j-p9v4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-49574"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/issues/48227"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/pull/48486"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/commit/2b58f59f4bf0bae7d35b1abb585b65f2a66787d1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/commit/31e8a3bfcf4e223788615d5ce25eb929ca251275"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/commit/d1ee57e7b826872b6355cfec0ae13465840e232c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/quarkusio/quarkus"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/releases/tag/3.24.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-668" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-06-23T18:53:22Z",
    "nvd_published_at" : "2025-06-23T20:15:28Z"
  }
}