# CVE-2025-49574: Quarkus potential data leak when duplicating a duplicated context

> Attackers may access sensitive data from other transactions due to context duplication flaws in Quarkus applications.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2025
- **Updated:** 22 Dec 2025
- **Also known as:** CLEANSTART-2026-HN92795, CLEANSTART-2026-LG13254, ECHO-49d8-ee3f-6de3, GHSA-9623-mj7j-p9v4, MINI-fcvq-9cxf-w5j7

## What is CVE-2025-49574?

CVE-2025-49574 is a medium-severity vulnerability in quarkusio quarkus, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2025-49574?

6 open source packages ship an affected version, including io.quarkus:quarkus-vertx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-vertx` | Maven | All versions | 3.15.6 |
| `io.quarkus:quarkus-vertx` | Maven | All versions | 3.15.6 |
| `io.quarkus:quarkus-vertx` | Maven | From 3.16.0.CR1 | 3.20.2 |
| `io.quarkus:quarkus-vertx` | Maven | From 3.16.0.CR1 | 3.20.2 |
| `io.quarkus:quarkus-vertx` | Maven | From 3.21.0.CR1 | 3.24.1 |
| `io.quarkus:quarkus-vertx` | Maven | From 3.21.0.CR1 | 3.24.1 |

## How do I fix CVE-2025-49574?

Upgrade io.quarkus:quarkus-vertx to a fixed version for your release line: 3.15.6, 3.20.2 or 3.24.1.

## Is CVE-2025-49574 being exploited?

There is no known exploitation of CVE-2025-49574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49574 and fix it if it is affected.

What it is: CVE-2025-49574 is a medium-severity vulnerability in quarkusio quarkus, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49574 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-vertx (Maven): affected all versions; fixed in 3.15.6
- io.quarkus:quarkus-vertx (Maven): affected all versions; fixed in 3.15.6
- io.quarkus:quarkus-vertx (Maven): affected from 3.16.0.CR1; fixed in 3.20.2
- io.quarkus:quarkus-vertx (Maven): affected from 3.16.0.CR1; fixed in 3.20.2
- io.quarkus:quarkus-vertx (Maven): affected from 3.21.0.CR1; fixed in 3.24.1
- io.quarkus:quarkus-vertx (Maven): affected from 3.21.0.CR1; fixed in 3.24.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49574/ (Markdown: https://insights.sbomify.com/CVE-2025-49574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49574
- OSV: https://osv.dev/vulnerability/CVE-2025-49574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49574/
Summaries are generated and may contain mistakes; the official description above is the record.