Cross-request data exposure via shared endpoint instances
Published Feb 13, 2025 · Updated Aug 4, 2026
Data exposure in Quarkus REST before 3.18.2 allows remote authenticated users to receive another request's parameters during concurrency. Unscoped REST resource classes reuse an endpoint instance, so field-injected headers and other request parameters retain values across requests. Exploitation requires concurrent access to an affected endpoint that uses field injection without request scope, enabling data access, request manipulation, or user impersonation.
Summary
What happened
Data exposure in Quarkus REST before 3.18.2 allows remote authenticated users to receive another request's parameters during concurrency. Unscoped REST resource classes reuse an endpoint instance, so field-injected headers and other request parameters retain values across requests. Exploitation requires concurrent access to an affected endpoint that uses field injection without request scope, enabling data access, request manipulation, or user impersonation.
The record
- CVE
- CVE-2025-1247
- Published
- Feb 13, 2025
- Updated
- Aug 4, 2026
- Vendor
- Quarkus
- Product
- Quarkus REST
- Classifications
- CWE-488, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2025CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.18.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo