Security readout for executives and security teams
Plain-English summary
Apache Camel can wrongly trust certain HTTP headers on CXF or Knative routes. An unauthenticated attacker may inject internal Camel headers that change downstream behavior. In risky routes, that can lead to remote code execution or arbitrary file writes.
Executive priority
Treat this as urgent for internet-facing or partner-facing Camel integrations. Prioritize systems that process HTTP requests and invoke file, execution, or other header-controlled components. The business risk is system compromise or data modification if vulnerable routing patterns exist.
Technical view
The cited issue is missing inbound filtering in CxfRsHeaderFilterStrategy, CxfHeaderFilterStrategy, and KnativeHttpHeaderFilterStrategy. Camel-internal headers can enter via CXF-RS, CXF-SOAP, or Knative HTTP endpoints and influence header-driven components such as camel-exec or camel-file.
Likely exposure
Exposure is likely where affected Apache Camel versions expose CXF-RS, CXF-SOAP, or Knative HTTP endpoints to untrusted clients and route messages to header-driven components. Affected ranges are 3.18.0 before 4.14.6 and 4.15.0 before 4.18.2.
Exploitation context
The source bundle states unauthenticated network exploitation with low complexity and severe impact. KEV is false, and the supplied sources do not establish active exploitation. Exploitability depends on route design, especially forwarding attacker-controlled headers into components that honor those headers.
Researcher notes
The advisory links this to previous Camel header-filtering patterns, but this CVE concerns CXF and Knative strategies. Evidence names concrete vulnerable filtering behavior and fixed versions. Product/package metadata is not exhaustive enough to assume every Camel deployment is exposed.
Mitigation direction
- Upgrade to Apache Camel 4.19.0 where feasible.
- If on 4.18.x LTS, upgrade to 4.18.2.
- If on 4.14.x LTS, upgrade to 4.14.6.
- Restrict untrusted access to affected HTTP endpoints until upgrades are complete.
- Review vendor guidance before relying on compensating controls.
Validation and detection
- Inventory Apache Camel versions and identify affected release ranges.
- Search deployments for camel-cxf-rest, camel-cxf-transport, and camel-knative-http usage.
- Review routes from CXF or Knative HTTP endpoints to header-driven components.
- Check whether camel-exec or camel-file receive headers from external requests.
- Confirm patched versions are deployed in runtime artifacts, not only source files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-178: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-791: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47323 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-19T14:02:59.056Z: Reported to Red Hat.
- 2026-05-19T12:25:49.373Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://camel.apache.org/security/CVE-2026-47323.htmlCVE reference, apache · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-47323CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2479869CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-47323.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Handling of Case Sensitivity
Improper Handling of Case Sensitivity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incomplete Filtering of Special Elements
Incomplete Filtering of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.