See how apache software foundation compares to other vendors in security performance
Last updated 4 September 2026
Latest version: 2.19.0
Latest version: 5.1.2
End of life: 8/11/2027, Latest version: 4.22.0
Deserialization of Untrusted Data (CWE-502) in the Tribes-based clustering component
in Apache Software Foundation Apache Axis2/Java through 2.0.0 on Apache Tomcat
(only when Tribes clustering is enabled, which is off by default) allows an
unauthenticated remote attacker with network access to the clustering port to
execute arbitrary code via a crafted serialized Java object delivered to the cluster
channel and deserialized in
org.apache.axis2.clustering.tribes.Axis2ChannelListener#messageReceived. Users are
recommended to upgrade to version 2.0.1, which fixes this issue by removing the
clustering feature entirely.
Latest version: 3.0.0
Severity: low
Affected versions:
- Apache Axis2/Java through 2.0.0
Description:
Deserialization of Untrusted Data (CWE-502) in the Tribes-based clustering component
in Apache Software Foundation Apache Axis2/Java through 2.0.0 on Apache Tomcat
(only when Tribes clustering is enabled, which is off by default) allows an
unauthenticated remote attacker with network access to the clustering port to
execute arbitrary code via a crafted serialized Java object delivered to the cluster
channel and deserialized in
org.apache.axis2.clustering.tribes.Axis2ChannelListener#messageReceived. Users are
recommended to upgrade to version 2.0.1, which fixes this issue by removing the
clustering feature entirely.
Credit:
liuhuajin of Huawei (finder)
References:
https://github.com/apache/axis-axis2-java-core/commit/e6f53b230bddcb40577c84ff290ba51e7265fa15 https://axis.apache.org/ https://www.cve.org/CVERecord?id=CVE-2026-66713
Latest version: 6.3.2
Apache Traffic Server is vulnerable to stalled HTTP/2 flow-control.
CVE: CVE-2026-59173 - DoS vulnerability in HTTP/2 via stalled flow-control conditions
Severity: important
Reported By: Okta Red Team
Vendor: The Apache Software Foundation
Version Affected: ATS 9.0.0 to 9.2.13 ATS 10.0.0 to 10.1.2
Mitigation: 9.x users should upgrade to 9.2.14 or later versions 10.x users should upgrade to 10.1.3 or later versions
Reference: https://www.cve.org/CVERecord?id=CVE-2026-59173
End of life: 1/11/2028, Latest version: 4.2.0
Improper Input Validation vulnerability in Apache Camel Cometd Component.
The camel-cometd component maps inbound Bayeux (CometD) message headers into the Camel Exchange without applying a HeaderFilterStrategy. CometdBinding.populateExchangeFromMessage copies the entire ext.CamelHeaders map supplied by the CometD client directly onto the Camel message (message.setHeaders), so any header name - including Camel-internal control headers such as CamelHttpUri, CamelFileName or CamelJmsDestinationName - is accepted unmodified. Because a CometdComponent installs no Bayeux SecurityPolicy by default, any client that can complete the Bayeux handshake against the CometD endpoint can publish such a message without authentication. An attacker can therefore inject arbitrary Camel control headers that influence the behaviour of downstream producers in the route (for example redirecting an HTTP producer, changing a file name, or overriding a JMS destination); the injected headers also persist across internal direct, seda and vm hops. The concrete downstream impact depends on which producers the route uses. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix implements a HeaderFilterStrategy in the camel-cometd binding (a long-standing TODO in the code) that filters the Camel header namespace case-insensitively on inbound mapping, so client-supplied Camel / camel headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from inbound CometD messages before they reach any downstream producer (for example removeHeaders('Camel') and removeHeaders('camel') at the start of the route), and install an explicit Bayeux SecurityPolicy on the CometdComponent so that only authenticated clients can publish.
Latest version: 3.3.1
End of life: 8/11/2026, Latest version: 4.21.0
End of life: 8/17/2026, Latest version: 2.18.1
Latest version: 4.3.1
End of life: 6/26/2026, Latest version: 4.20.0
End of life: 4/23/2026, Latest version: 4.19.0
End of life: 7/6/2026, End of support: 7/6/2026, Latest version: 3.2.2
Latest version: 3.5.0
Latest version: 10.0.0
End of life: 2/17/2027, Latest version: 4.18.4
Latest version: 4.2.1
End of life: 6/1/2026, Latest version: 2.17.0
End of life: 2/17/2026, Latest version: 4.17.0
End of life: 6/11/2027, Latest version: 4.1.3
End of life: 2/6/2026, Latest version: 2.16.0
Latest version: 6.2.9
End of life: 1/12/2026, Latest version: 4.16.0
End of life: 11/5/2025, Latest version: 4.15.0
End of life: 4/7/2026, End of support: 4/7/2026, Latest version: 3.1.8