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

CVE-2023-5675 — quarkus-resteasy-reactive…

MEDIUMFix: quarkusio/quarkus@b7dd69a

CVE-2023-5675 is a medium-severity (CVSS 6.5) CWE-285 vulnerability in io.quarkus:quarkus-resteasy-reactive-common-deployment. A fix is available for io.quarkus:quarkus-resteasy-reactive-common-deployment — see the affected versions and patch details below.

Quarkus: authorization flaw in quarkus resteasy reactive and classic

Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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-2023-5675.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk
0.00%0.32%0.64%0.96%0.1%0.5%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-resteasy-reactive-common-deployment☕io.quarkus:quarkus-resteasy-reactive-common☕io.quarkus:quarkus-resteasy-reactive-common-deployment☕io.quarkus:quarkus-resteasy-reactive-common☕io.quarkus:quarkus-resteasy-reactive-common-deployment☕io.quarkus:quarkus-resteasy-reactive-common

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. When a Quarkus RestEasy Classic or Reactive JAX-RS endpoint has its methods declared in the abstract Java class or customized by Quarkus extensions using the annotation processor, the authorization of these methods will not be enforced if it is enabled by either 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' properties.

While backports of this fix exist in versions 3.6.9 and 3.7.1 users of older versions are encouraged to update to the 3.8.x LTS branch.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.quarkus:quarkus-resteasy-reactive-common-deploymentall versions3.2.10.Finalio.quarkus:quarkus-resteasy-reactive-common-deployment:3.2.10.Final
☕Mavenio.quarkus:quarkus-resteasy-reactive-commonall versions3.2.10.Finalio.quarkus:quarkus-resteasy-reactive-common:3.2.10.Final
☕Mavenio.quarkus:quarkus-resteasy-reactive-common-deployment≥ 3.3.0&&< 3.6.93.6.9io.quarkus:quarkus-resteasy-reactive-common-deployment:3.6.9
☕Mavenio.quarkus:quarkus-resteasy-reactive-common≥ 3.3.0&&< 3.6.93.6.9io.quarkus:quarkus-resteasy-reactive-common:3.6.9
☕Mavenio.quarkus:quarkus-resteasy-reactive-common-deployment≥ 3.7.0&&< 3.7.13.7.1io.quarkus:quarkus-resteasy-reactive-common-deployment:3.7.1
☕Mavenio.quarkus:quarkus-resteasy-reactive-common≥ 3.7.0&&< 3.7.13.7.1io.quarkus:quarkus-resteasy-reactive-common:3.7.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-resteasy-reactive-common-deployment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.2.10.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-5675 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 HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't 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-2023-5675 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Quarkus 2.13.9.Finalio.quarkus/quarkus-resteasy:2.13.9.Final-redhat-00003RHSA-2024:0494
Red Hat build of Quarkus 3.2.9.Finalio.quarkus/quarkus-resteasy:3.2.9.Final-redhat-00003RHSA-2024:0495

Frequently Asked Questions

A flaw was found in Quarkus. When a Quarkus RestEasy Classic or Reactive JAX-RS endpoint has its methods declared in the abstract Java class or customized by Quarkus extensions using the annotation processor, the authorization of these methods will not be enforced if it is enabled by either 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' properties. While backports of this fix exist in versions 3.6.9 and 3.7.1 users of older versions are encouraged to update to the 3.8.x LTS branch.
O3 Security · Impact-Aware SCA

Is CVE-2023-5675 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-5675: quarkus-resteasy — Fixed in 3.2.10.Final