{"id":"CVE-2026-84181","title":"Apache Camel: Camel-Shiro Authentication Bypass via Skipped Credential Verification on Subject Reuse","summary":"Improper Authentication vulnerability in Apache Camel Shiro component.\n\n\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe Shiro security processor skipped credential verification when the subjec…","severity":"medium","cvss":5.9,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","cvssSource":"cna","cwe":["CWE-287"],"vendor":"Apache Software Foundation","product":"org.apache.camel:camel-shiro","affected":["org.apache.camel:camel-shiro >= 4.0.0 < 4.18.5","org.apache.camel:camel-shiro >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:31:41.671Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-84181","references":[{"url":"https://camel.apache.org/security/CVE-2026-84181.html","label":"Apache Camel Security Advisory - CVE-2026-84181"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24439","label":"CAMEL-24439"},{"url":"https://github.com/apache/camel/pull/25822","label":"Fix on main, released in 4.23.0 (commit 6f72ae648eb0c6e54a913f7be33cd2c020355b95)"},{"url":"https://github.com/apache/camel/pull/25944","label":"Backport to camel-4.22.x, released in 4.22.1 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666)"},{"url":"https://github.com/apache/camel/pull/25946","label":"Backport to camel-4.18.x, released in 4.18.5 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.817Z","slug":"CVE-2026-84181","body":"## Overview\n\nImproper Authentication vulnerability in Apache Camel Shiro component.\n\n\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe 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.\n\nUpgrade 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.\n\n## Affected\n\n- `org.apache.camel:camel-shiro >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-shiro >= 4.19.0 < 4.22.1`\n\n## Remediation\n\nUpgrade 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.\n\n### Workarounds\n\nFor 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.","depth":"sunlit","depthScore":32,"depthScoreParts":{"impact":32.5,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}