Apache Camel patches XXE, deserialization, and credential flaws
Saxon needs 4.18.5, 4.22.2, or 4.23.0; stopping at the XPath and Smooks fix 4.22.1 misses it.
Saxon needs 4.18.5, 4.22.2, or 4.23.0; stopping at the XPath and Smooks fix 4.22.1 misses it.
Eight critical and high issues span Camel K and Camel components, with fixes that differ by branch.
Unmuted consumer exceptions in camel-coap can expose sensitive information to unauthenticated remote users; CVSS is 5.3.
A low-privileged attacker can inject expressions through the CamelAwsS3Key header; the CVSS score is 5.4.
Cached introspection results are not limited by token expiry, so expired access tokens can still be accepted.
A low-privileged caller can steer conversion output to an arbitrary directory through an unvalidated header.
Path checks added after CVE-2026-40047 do not reject absolute paths supplied as custom CLI arguments.
camel-oauth from 4.19.0 before 4.22.2 can reuse client-credentials bearer tokens; CVSS 3.1 is 4.8.
camel-saxon before 4.18.5 and before 4.22.2 parses Source bodies with Saxon defaults; CVSS is 7.5.
CVE-2026-88900 scores CVSS 8.8; fixed builds are 4.18.5 and 4.22.1.
The 4.14.x line is end of life and does not receive these fixes.
Peter Gutmann backs splitting oss-security so Apache CVE floods do not bury the main list.
Entities are extracted by the model from each article. First seen , last mentioned . Watching keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.
Today 617 readers · 742 views · 563 reads · all time 158K views