Read the docs
TI-2026-76347 Aliases CVE-2026-84181GHSA-xwpw-3mm7-243x

Apache Camel Shiro component skips credential check on subject reuse

Priority LOW 27CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-287.

Summary

Apache Camel from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1 is affected. The Shiro security processor skips credential verification when the subject bound to the current thread has the same principal as the incoming exchange, and pooled threads reuse those subjects across exchanges (CWE-287). A remote, unauthenticated attacker can send a request naming an active principal and have the presented password go unverified.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00505 43rd percentileScored 2026-11-07
Fix Partial Apache Camel (Apache Software Foundation): 4.18.5, 4.22.1, 4.23.0Red Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Camel4.0.0 to before 4.18.5; 4.19.0 to before 4.22.14.18.5, 4.22.1, 4.23.0Patch availableCNA
  • Apache Camel VendorApache Affected 4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1 Fixed in 4.18.5, 4.22.1, 4.23.0 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1VulnerableApache
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* Versions 4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1 Vulnerable ·Apache

Remediation

Upgrade to Apache Camel 4.23.0, or to 4.18.5 on the 4.18.x LTS stream or 4.22.1 on the 4.22.x LTS stream. Red Hat Fuse 7 has no fix planned. Where upgrading is not possible, clear the Shiro subject from the thread at the end of every exchange.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.18.5, 4.22.1, 4.23.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Apache Camel 4.18.5, 4.22.1

    39 records Highest priority Priority HIGH 6 HIGH, 9 MEDIUM, 24 LOW

    Other records, highest priority first

    • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcastPriority HIGH 82
    • TI-2026-76339 Path traversal in Apache Camel azure-files componentPriority HIGH 74
    • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directoryPriority HIGH 74
    Show all 39 records →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Fuse 7AffectedNo fix planned: Out of support scope

Timeline

  1. 2026-10-19 Threatist record created from CVE-2026-84181
  2. 2026-10-19 Alias added: GHSA-xwpw-3mm7-243x
  3. 2026-10-20 CISA SSVC decision points changed
  4. 2026-10-20 Priority changed: MEDIUM → LOW
  5. 2026-11-04 Affected versions changed · Red Hat
  6. 2026-11-04 CVSS score added · Red Hat

References

Patch 4

Advisory 1

  • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
  • TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
  • TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
  • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
  • TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
  • TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
See all 116 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences