# CVE-2025-1247: Io.quarkus:quarkus-rest: quarkus rest endpoint request parameter leakage due to shared instance > Attackers can access sensitive request parameters from other users due to shared instances in Quarkus REST endpoints lacking proper CDI scopes. - **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Feb 2025 - **Updated:** 20 Oct 2026 - **Also known as:** GHSA-phg3-gv66-q38x ## What is CVE-2025-1247? CVE-2025-1247 is a high-severity vulnerability in Red Hat Build of Apache Camel 4.8 for Quarkus 3.15, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in Quarkus REST that allows request parameters to leak between concurrent requests if endpoints use field injection without a CDI scope. This vulnerability allows attackers to manipulate request data, impersonate users, or access sensitive information. Weakness: CWE-488 (Exposure of Data Element to Wrong Session) ## Which versions are affected by CVE-2025-1247? 12 open source packages ship an affected version, including io.quarkus:quarkus-rest and io.quarkus:quarkus-rest-deployment. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.quarkus:quarkus-rest` | Maven | All versions | 3.8.6.1 | | `io.quarkus:quarkus-rest` | Maven | All versions | 3.8.6.1 | | `io.quarkus:quarkus-rest` | Maven | From 3.16.0.CR1 | 3.18.2 | | `io.quarkus:quarkus-rest` | Maven | From 3.16.0.CR1 | 3.18.2 | | `io.quarkus:quarkus-rest` | Maven | From 3.9.0.CR1 | 3.15.3.1 | | `io.quarkus:quarkus-rest` | Maven | From 3.9.0.CR1 | 3.15.3.1 | | `io.quarkus:quarkus-rest-deployment` | Maven | All versions | 3.8.6.1 | | `io.quarkus:quarkus-rest-deployment` | Maven | All versions | 3.8.6.1 | | `io.quarkus:quarkus-rest-deployment` | Maven | From 3.16.0.CR1 | 3.18.2 | | `io.quarkus:quarkus-rest-deployment` | Maven | From 3.16.0.CR1 | 3.18.2 | | `io.quarkus:quarkus-rest-deployment` | Maven | From 3.9.0.CR1 | 3.15.3.1 | | `io.quarkus:quarkus-rest-deployment` | Maven | From 3.9.0.CR1 | 3.15.3.1 | ## How do I fix CVE-2025-1247? Upgrade io.quarkus:quarkus-rest to a fixed version for your release line: 3.8.6.1, 3.18.2 or 3.15.3.1. ## Is CVE-2025-1247 being exploited? There is no known exploitation of CVE-2025-1247 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-1247 and fix it if it is affected. What it is: CVE-2025-1247 is a high-severity vulnerability in Red Hat Build of Apache Camel 4.8 for Quarkus 3.15, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-1247 in the wild and no public exploit code. Affected packages and fixed versions: - io.quarkus:quarkus-rest (Maven): affected all versions; fixed in 3.8.6.1 - io.quarkus:quarkus-rest (Maven): affected all versions; fixed in 3.8.6.1 - io.quarkus:quarkus-rest (Maven): affected from 3.16.0.CR1; fixed in 3.18.2 - io.quarkus:quarkus-rest (Maven): affected from 3.16.0.CR1; fixed in 3.18.2 - io.quarkus:quarkus-rest (Maven): affected from 3.9.0.CR1; fixed in 3.15.3.1 - io.quarkus:quarkus-rest (Maven): affected from 3.9.0.CR1; fixed in 3.15.3.1 - io.quarkus:quarkus-rest-deployment (Maven): affected all versions; fixed in 3.8.6.1 - io.quarkus:quarkus-rest-deployment (Maven): affected all versions; fixed in 3.8.6.1 - io.quarkus:quarkus-rest-deployment (Maven): affected from 3.16.0.CR1; fixed in 3.18.2 - io.quarkus:quarkus-rest-deployment (Maven): affected from 3.16.0.CR1; fixed in 3.18.2 - io.quarkus:quarkus-rest-deployment (Maven): affected from 3.9.0.CR1; fixed in 3.15.3.1 - io.quarkus:quarkus-rest-deployment (Maven): affected from 3.9.0.CR1; fixed in 3.15.3.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-1247/ (Markdown: https://insights.sbomify.com/CVE-2025-1247/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1247 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1247 - OSV: https://osv.dev/vulnerability/CVE-2025-1247 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-1247/ Summaries are generated and may contain mistakes; the official description above is the record.