Quarkus: http security policy bypass

Description

A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.

Scores

EPSS (exploitation in 30 days)

2.3% · top 17% of all CVEs (6 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Weakness

• CWE-148: Improper Neutralization of Input Leaders (opens in a new tab)All about CWE-148 and its CVEs
• CWE-863 (opens in a new tab)All about CWE-863 and its CVEs

Affected products

• Red Hat · Openshift Serverless 1 on RHEL 8

  • unaffected 0:1.9.2-3.el8 – < *

• Red Hat · Red Hat build of OptaPlanner 8

  All versions: unaffected

• Red Hat · Red Hat build of Quarkus 2.13.8.SP2

  • unaffected 2.13.8.Final-redhat-00005 – < *

• Red Hat · Red Hat build of Quarkus 2.13.8.SP2

  • unaffected 2.13.8.Final-redhat-00005 – < *

• Red Hat · Red Hat build of Quarkus 2.13.8.SP2

  • unaffected 2.13.8.Final-redhat-00005 – < *

• Red Hat · Red Hat Camel Extensions for Quarkus 2.13.3-1

  All versions: unaffected

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.9.2-3 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.1-1 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.1-1 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.9.2-3 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.1-1 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.1-1 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.1-1 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.0-5 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.0-6 – < *

• Red Hat · Red Hat OpenShift Serverless 1.30

  • unaffected 1.30.0-6 – < *

• Red Hat · RHEL-8 based Middleware Containers

  • unaffected 7.13.4-3 – < *

• Red Hat · RHEL-8 based Middleware Containers

  • unaffected 7.13.4-2 – < *

• Red Hat · RHEL-8 based Middleware Containers

  • unaffected 7.13.4-2 – < *

• Red Hat · RHEL-8 based Middleware Containers

  • unaffected 7.13.4-3 – < *

• Red Hat · RHEL-8 based Middleware Containers

  • unaffected 7.13.4-3 – < *

• Red Hat · RHINT Camel-K-1.10.2

  All versions: unaffected

• Red Hat · RHINT Service Registry 2.5.4 GA

  All versions: unaffected

• Red Hat · RHPAM 7.13.4 async

  All versions: unaffected

• Red Hat · Red Hat build of Quarkus

  All versions: affected

• Red Hat · Red Hat build of Quarkus

  All versions: affected

• Red Hat · Red Hat Integration Camel Quarkus 2

  All versions: affected

• Red Hat · Red Hat Process Automation 7

  All versions: affected

Affected packages

From reviewed advisories of the GitHub Advisory Database.

• Mavenio.quarkus:quarkus-csrf-reactiveGHSA-4f4r-wgv2-jjvg (opens in a new tab)
• Mavenio.quarkus:quarkus-keycloak-authorizationGHSA-4f4r-wgv2-jjvg (opens in a new tab)
• Mavenio.quarkus:quarkus-undertowGHSA-4f4r-wgv2-jjvg (opens in a new tab)
• Mavenio.quarkus:quarkus-vertx-httpGHSA-4f4r-wgv2-jjvg (opens in a new tab)

What to do

Workaround: Use a ‘deny’ wildcard for base paths, then authenticate specifics within that: Examples: ``` deny: /* authenticated: /services/* ``` or ``` deny: /services/* roles-allowed: /services/rbac/* ``` NOTE: Products are only vulnerable if they use (or allow use of) path-based HTTP policy configuration. Products may also be affected–shipping the component in question–without being vulnerable (“affected at reduced impact”). See https://access.redhat.com/security/vulnerabilities/RHSB-2023-002 for more detailed mitigations.

References (12)

• RHSA-2023:5170 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:5310 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:5337 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:5446 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:5479 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:5480 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:6107 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:6112 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• RHSA-2023:7653 (opens in a new tab)vendor-advisoryx_refsource_REDHATx_transferred
• https://access.redhat.com/security/cve/CVE-2023-4853 (opens in a new tab)vdb-entryx_refsource_REDHATx_transferred
• RHSB-2023-002 (opens in a new tab)technical-descriptionx_refsource_REDHATx_transferred
• RHBZ#2238034 (opens in a new tab)issue-trackingx_refsource_REDHATx_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisory GHSA-4f4r-wgv2-jjvg (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2023-4853](https://trackcve.app/badge/CVE-2023-4853.svg)](https://trackcve.app/cve/CVE-2023-4853)

Record last updated 4 Nov 2026, 20:54 UTC.