CVE-2026-53913: Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') v

Q: How do I fix CVE-2026-53913?

camel: upgrade to 4.18.3, 4.21.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-53913 being exploited?

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

Q: What does CVE-2026-53913 affect?

CVE-2026-53913 affects camel. Severity is critical (CVSS 9.8). Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component. The KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakS

Q: How urgent is CVE-2026-53913?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2026-53913 is a critical-severity flaw (CVSS 9.8) affecting camel. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component. The KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requi

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-287, CWE-306, CWE-636
Published	2026-07-06
Last modified	2026-07-09

Publisher (CNA): Apache Software Foundation · Vendor: apache

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

Am I affected?

Timeline

2026-07-06 09:16 UTCPublished CVE record published
2026-07-09 03:03 UTCUpdated Record last modified

apache camel UPGRADE

Affected: >= 4.15.0 and < 4.18.3 · >= 4.19.0 and < 4.21.0

Fixed in: 4.18.3, 4.21.0

Safe to downgrade to: a release before 4.15.0

1. Check installed version

apt-cache policy camel || rpm -q camel || camel --version

2. UPGRADE to 4.18.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade camel

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade camel

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 4.15.0 (Debian / Ubuntu)

apt-cache madison camel sudo apt install camel=<VERSION_BEFORE_4.15.0> sudo apt-mark hold camel

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list camel sudo dnf downgrade camel-<VERSION_BEFORE_4.15.0> sudo dnf versionlock add camel

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.

Exact fixes by distribution

Maven · org.apache.camel:camel-keycloak · FIXED · 4.18.3 · vulnerable: >= 4.15.0, < 4.18.3 · source

Set org.apache.camel:camel-keycloak to 4.18.3 or later in pom.xml or build.gradle, then rebuild and redeploy.

Fedora 46 · rubygem-mechanize · FIXED · 2.14.2-1.fc46 · FEDORA-2026-d2e3b5fc5d · source

sudo dnf upgrade --advisory=FEDORA-2026-d2e3b5fc5d

Fedora ELN · opkssh · FIXED · 0.19.1-1.eln159 · FEDORA-2026-45a9706969 · source

sudo dnf upgrade --advisory=FEDORA-2026-45a9706969

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: oscerd/CVE-2026-53913 (1 stars)

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-2026-53913?

camel: upgrade to 4.18.3, 4.21.0. Exact commands for each OS are on this page.

Is CVE-2026-53913 being exploited?

CVE-2026-53913 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-2026-53913 affect?

CVE-2026-53913 affects camel. Severity is critical (CVSS 9.8). Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component. The KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakS

How urgent is CVE-2026-53913?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Keycloak vulnerabilities

Related CVEs

CVE-2026-33453 CRITICAL 10.0 UPGRADE Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel C
CVE-2026-40860 CRITICAL 9.8 UPGRADE JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized
CVE-2026-33454 CRITICAL 9.4 UPGRADE The Camel-Mail component is vulnerable to Camel message header injection
CVE-2026-40453 CRITICAL 9.9 UPGRADE The fix for CVE-2025-27636 added setLowerCase(true) to HttpHeaderFilterStrategy so that case-variant header na
CVE-2026-40473 HIGH 8.8 UPGRADE The camel-mina component's MinaConverter.toObjectInput(IoBuffer) type converter wraps an IoBuffer in a java.io

References

← Back to latest CVEs