CVE-2025-1247 is a high-severity (CVSS 8.3) CWE-488 vulnerability in io.quarkus:quarkus-rest. A fix is available for io.quarkus:quarkus-rest — see the affected versions and patch details below.
Io.quarkus:quarkus-rest: quarkus rest endpoint request parameter leakage due to shared instance
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-1247.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-1247 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.quarkus:quarkus-rest☕io.quarkus:quarkus-rest-deployment☕io.quarkus:quarkus-rest☕io.quarkus:quarkus-rest-deployment☕io.quarkus:quarkus-rest☕io.quarkus:quarkus-rest-deploymentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-rest | ≥ 3.16.0.CR1&&< 3.18.2 | 3.18.2io.quarkus:quarkus-rest:3.18.2 |
| ☕Maven | io.quarkus:quarkus-rest-deployment | ≥ 3.16.0.CR1&&< 3.18.2 | 3.18.2io.quarkus:quarkus-rest-deployment:3.18.2 |
| ☕Maven | io.quarkus:quarkus-rest | ≥ 3.9.0.CR1&&< 3.15.3.1 | 3.15.3.1io.quarkus:quarkus-rest:3.15.3.1 |
| ☕Maven | io.quarkus:quarkus-rest-deployment | ≥ 3.9.0.CR1&&< 3.15.3.1 | 3.15.3.1io.quarkus:quarkus-rest-deployment:3.15.3.1 |
| ☕Maven | io.quarkus:quarkus-rest | all versions | 3.8.6.1io.quarkus:quarkus-rest:3.8.6.1 |
| ☕Maven | io.quarkus:quarkus-rest-deployment | all versions | 3.8.6.1io.quarkus:quarkus-rest-deployment:3.8.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-rest to 3.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-1247 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-1247 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-1247. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability marked as important severity rather than moderate because it leads to cross-request data leakage, which can compromise the confidentiality and integrity of user interactions. In a concurrent environment, multiple requests being served by a single, shared instance of an endpoint class means that…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 | quarkus-rest | RHSA-2025:2067 |
| Red Hat build of Quarkus 3.15.3.SP1 | quarkus-rest | RHSA-2025:1885 |
| Red Hat build of Quarkus 3.8.6.SP3 | quarkus-rest | RHSA-2025:1884 |
Frequently Asked Questions
Is CVE-2025-1247 in your dependencies?
O3 Security finds CVE-2025-1247 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.