Description
Improper Authentication vulnerability in Apache Camel Shiro component.



This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.

The Shiro security processor skipped credential verification when the subject already bound to the current thread carried the same principal as the incoming exchange. Because the thread that carries a Camel exchange is drawn from a pool and reused across exchanges, a subject left bound by an earlier authenticated exchange could satisfy the check for a later one that presented no valid credentials of its own. The password on the incoming exchange was, in that case, never verified. The condition depends on thread reuse and on the principal matching, which is why it is not reached on every request, but it requires nothing of the attacker beyond sending a request naming a principal that is in active use.

Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The processor now verifies the presented credentials on every exchange rather than accepting a subject already bound to the thread. Setting alwaysReauthenticate=false restores the previous behaviour for deployments that depend on it. For deployments that cannot upgrade immediately, ensure the Shiro subject is cleared from the thread at the end of every exchange so that no subject can be inherited by a later one.
Published: 2026-10-19
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: Authentication Bypass allowing unauthorized access
Action: Immediate Patch
AI Analysis

Impact

Apache Camel’s Shiro component can bypass authentication when a security subject is already bound to the thread that handles a Camel exchange. If the same principal is present on the thread from an earlier validated request, the component incorrectly skips credential verification for a subsequent request that supplies no valid credentials. This flaw, identified as CWE-287, enables an attacker to gain unauthorized access by crafting a request that references a principal already authenticated on the reused thread, without needing to know the user’s password.

Affected Systems

The vulnerability impacts all Apache Camel releases from 4.0.0 up to but not including 4.18.5 and from 4.19.0 up to but not including 4.22.1. The affected system is the Apache Camel framework’s Shiro processor; thread reuse across exchanges creates the risk window.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity, and the EPSS score is not available, suggesting no current exploitation data. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires only that the attacker send a request naming a principal that is currently authenticated on the thread, and that the application’s thread pool reuses the same thread across exchanges. No privileged credentials are needed, making the attack path feasible via network traffic to the Camel service. Overall risk is moderate, with a clear path for unauthorized access if not mitigated.

Generated by OpenCVE AI on October 19, 2026 at 11:37 UTC.

Remediation

Vendor Solution

Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The processor now verifies the presented credentials on every exchange rather than accepting a subject already bound to the thread. Setting alwaysReauthenticate=false restores the previous behaviour for deployments that depend on it.


Vendor Workaround

For deployments that cannot upgrade immediately, ensure the Shiro subject is cleared from the thread at the end of every exchange so that no subject can be inherited by a later one.


OpenCVE Recommended Actions

  • Upgrade Apache Camel to version 4.23.0; for the 4.18.x LTS stream upgrade to 4.18.5 and for the 4.22.x LTS stream upgrade to 4.22.1, which enforce credential verification on each exchange.
  • If an immediate upgrade is not possible, configure the application to clear the Shiro subject from the thread at the end of every exchange to prevent subject inheritance across exchanges.
  • Ensure that the Shiro processor is not set to alwaysReauthenticate=false, as that restores the unsafe behavior; enable always reauthentication so credentials are verified on every request.

Generated by OpenCVE AI on October 19, 2026 at 11:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache apache Camel
Apache camel
Vendors & Products Apache
Apache apache Camel
Apache camel

Mon, 19 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description Improper Authentication vulnerability in Apache Camel Shiro component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The Shiro security processor skipped credential verification when the subject already bound to the current thread carried the same principal as the incoming exchange. Because the thread that carries a Camel exchange is drawn from a pool and reused across exchanges, a subject left bound by an earlier authenticated exchange could satisfy the check for a later one that presented no valid credentials of its own. The password on the incoming exchange was, in that case, never verified. The condition depends on thread reuse and on the principal matching, which is why it is not reached on every request, but it requires nothing of the attacker beyond sending a request naming a principal that is in active use. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The processor now verifies the presented credentials on every exchange rather than accepting a subject already bound to the thread. Setting alwaysReauthenticate=false restores the previous behaviour for deployments that depend on it. For deployments that cannot upgrade immediately, ensure the Shiro subject is cleared from the thread at the end of every exchange so that no subject can be inherited by a later one.
Title Apache Camel: Camel-Shiro Authentication Bypass via Skipped Credential Verification on Subject Reuse
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

Apache Apache Camel Camel
cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:31:41.671Z

Reserved: 2026-09-01T09:29:30.775Z

Link: CVE-2026-84181

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T11:17:22.250

Modified: 2026-10-19T11:17:22.250

Link: CVE-2026-84181

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T16:30:13Z

Weaknesses