CVE-2023-6267: Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 54.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: io.quarkus.resteasy.reactive:resteasy-reactive (Maven) 3.2.9.Final, 2.13.9.Final.
Low priority for now. Upgrade to io.quarkus.resteasy.reactive:resteasy-reactive (Maven) 3.2.9.Final, 2.13.9.Final or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not happen with configuration based security.
- Published
- Jan 25, 2024
- Updated
- Nov 4, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-755
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · redhat
- 8.6
- 1.2 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| quarkus | quarkus | cpe:2.3:a:quarkus:quarkus |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- quarkus quarkusbefore 2.13.9
- quarkus quarkus3.0.0 and later · before 3.2.9
- quarkus quarkus2.13.9
- quarkus quarkus3.2.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat build of OptaPlanner 8
- all versionsaffected
Red Hat Red Hat build of Quarkus 2.13.9.Final
- 2.13.9.Final-redhat-00003 and laternot affected · rpm
Red Hat Red Hat build of Quarkus 3.2.9.Final
- 3.2.9.Final-redhat-00003 and laternot affected · rpm
Red Hat Red Hat Fuse 7
- all versionsunknown
Red Hat Red Hat Integration Camel K 1
- all versionsaffected
Red Hat Red Hat Integration Camel Quarkus 2
- all versionsunknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | io.quarkus.resteasy.reactive:resteasy-reactive | from 3.0.0.Final · before 3.2.9.Final | 3.2.9.Final |
| Maven | io.quarkus.resteasy.reactive:resteasy-reactive | before 2.13.9.Final | 2.13.9.Final |
Same product
quarkus: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-4116A vulnerability was found in quarkus.49Plan
- CVE-2022-2466It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior.40Plan
- CVE-2024-12225Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-5720Nov 15, 2023 · Quarkus: build env information disclosure via gradle plugin30Monitor
- ← EarlierCVE-2023-6394Dec 9, 2023 · Quarkus: graphql operations over websockets bypass36Monitor
- Later →CVE-2025-66560Jan 7, 2026 · Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:io.quarkus.resteasy.reactive:resteasy-reactive | 2.13.9.Final | Package registry (OSV) |
| Maven:io.quarkus.resteasy.reactive:resteasy-reactive | 3.2.9.Final | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-755 · Improper Handling of Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.