NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2025-1247 — quarkus-rest

HIGHFix: quarkusio/quarkus@02ff9ed

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

Also known asGHSA-phg3-gv66-q38x
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.00%0.44%0.88%1.32%0.0%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected
☕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-deployment

Real-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

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.quarkus:quarkus-rest≥ 3.16.0.CR1&&< 3.18.23.18.2io.quarkus:quarkus-rest:3.18.2
☕Mavenio.quarkus:quarkus-rest-deployment≥ 3.16.0.CR1&&< 3.18.23.18.2io.quarkus:quarkus-rest-deployment:3.18.2
☕Mavenio.quarkus:quarkus-rest≥ 3.9.0.CR1&&< 3.15.3.13.15.3.1io.quarkus:quarkus-rest:3.15.3.1
☕Mavenio.quarkus:quarkus-rest-deployment≥ 3.9.0.CR1&&< 3.15.3.13.15.3.1io.quarkus:quarkus-rest-deployment:3.15.3.1
☕Mavenio.quarkus:quarkus-restall versions3.8.6.1io.quarkus:quarkus-rest:3.8.6.1
☕Mavenio.quarkus:quarkus-rest-deploymentall versions3.8.6.1io.quarkus:quarkus-rest-deployment:3.8.6.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. 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.

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.

Red HatImportant

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…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2025-1247 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Build of Apache Camel 4.8 for Quarkus 3.15quarkus-restRHSA-2025:2067
Red Hat build of Quarkus 3.15.3.SP1quarkus-restRHSA-2025:1885
Red Hat build of Quarkus 3.8.6.SP3quarkus-restRHSA-2025:1884

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-1247 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2025-1247: quarkus-rest — Fixed in 3.18.2