Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-4853: A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations cor

62
This week
HIGH 8.1REMOTEWATCHLISTUPGRADEDOWNGRADEUPGRADE

CVE-2023-4853 is a high-severity flaw (CVSS 8.1) affecting quarkus, build of optaplanner, build of quarkus. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance1.4% (top 27%)
CISA exploited listNo
WeaknessCWE-148, CWE-863
Published2023-09-20
Last modified2026-08-04
Publisher (CNA): Red Hat, Inc. · Vendor: quarkus · redhat

Share: LinkedIn · X · Reddit

Last updated 2026-08-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

quarkus quarkus UPGRADE
Affected: < 2.16.11 · >= 3.2.0 and < 3.2.6 · >= 3.3.0 and < 3.3.3
Fixed in: 2.16.11, 3.2.6, 3.3.3
Safe to downgrade to: a release before 3.2.0
1. Check installed version
apt-cache policy quarkus || rpm -q quarkus || quarkus --version
2. UPGRADE to 2.16.11 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade quarkus
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade quarkus
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.2.0 (Debian / Ubuntu)
apt-cache madison quarkus sudo apt install quarkus=<VERSION_BEFORE_3.2.0> sudo apt-mark hold quarkus
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list quarkus sudo dnf downgrade quarkus-<VERSION_BEFORE_3.2.0> sudo dnf versionlock add quarkus
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat build of optaplanner DOWNGRADE
Affected: 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
1. Check installed version
apt-cache policy build-of-optaplanner || rpm -q build-of-optaplanner || build-of-optaplanner --version
2. No fixed release: DOWNGRADE to a release before 8.0 (Debian / Ubuntu)
apt-cache madison build-of-optaplanner sudo apt install build-of-optaplanner=<VERSION_BEFORE_8.0> sudo apt-mark hold build-of-optaplanner
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list build-of-optaplanner sudo dnf downgrade build-of-optaplanner-<VERSION_BEFORE_8.0> sudo dnf versionlock add build-of-optaplanner
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat build of quarkus UPGRADE
Affected: >= 2.13.0 and < 2.13.8
Fixed in: 2.13.8
Safe to downgrade to: a release before 2.13.0
1. Check installed version
apt-cache policy build-of-quarkus || rpm -q build-of-quarkus || build-of-quarkus --version
2. UPGRADE to 2.13.8 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade build-of-quarkus
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade build-of-quarkus
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.13.0 (Debian / Ubuntu)
apt-cache madison build-of-quarkus sudo apt install build-of-quarkus=<VERSION_BEFORE_2.13.0> sudo apt-mark hold build-of-quarkus
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list build-of-quarkus sudo dnf downgrade build-of-quarkus-<VERSION_BEFORE_2.13.0> sudo dnf versionlock add build-of-quarkus
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat decision manager DOWNGRADE
Affected: 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.0
1. Check installed version
apt-cache policy decision-manager || rpm -q decision-manager || decision-manager --version
2. No fixed release: DOWNGRADE to a release before 7.0 (Debian / Ubuntu)
apt-cache madison decision-manager sudo apt install decision-manager=<VERSION_BEFORE_7.0> sudo apt-mark hold decision-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list decision-manager sudo dnf downgrade decision-manager-<VERSION_BEFORE_7.0> sudo dnf versionlock add decision-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat integration camel k UPGRADE
Affected: < 1.10.2
Fixed in: 1.10.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy integration-camel-k || rpm -q integration-camel-k || integration-camel-k --version
2. UPGRADE to 1.10.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade integration-camel-k
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade integration-camel-k
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat integration camel quarkus MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy integration-camel-quarkus || rpm -q integration-camel-quarkus || integration-camel-quarkus --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-4853?

quarkus: upgrade to 2.16.11, 3.2.6, 3.3.3; build of optaplanner: downgrade or apply the listed mitigation; build of quarkus: upgrade to 2.13.8. Exact commands for each OS are on this page.

Is CVE-2023-4853 being exploited?

CVE-2023-4853 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-4853 affect?

CVE-2023-4853 affects quarkus, build of optaplanner, build of quarkus. Severity is high (CVSS 8.1). 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

How urgent is CVE-2023-4853?

Priority 62/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.