Comparison Overview
KEBA Industrial Automation

KEBA Industrial Automation
Reindlstraße 51, Linz, Upper Austria, AT, 4040
Last Update: 02/04/2026
For more than 50 years KEBA has been developing and producing innovative automation solutions under the maxim “Automation by innovation” for a wide range of industries such as mechanical engineering and machine tools as well as for intralogistics, robotics, plastics, wi...

KUKA
Zugspitzstr. 140, Augsburg, 86165, DE
Last Update: 09/09/2026
KUKA SE & Co. KGaA is a global leader in intelligent automation solutions, generating around 3.7 billion euro in sales and employing approximately 15,000 people worldwide. Headquartered in Augsburg, Germany, KUKA’s mission is to make automation accessible for everyone -...
Compliance Ranges Comparison

KEBA Industrial Automation







KUKA






Benchmark & Cyber Underwriting Signals
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for KEBA Industrial Automation in 2026.
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for KUKA in 2026.
Incident History - KEBA Industrial Automation (X = Date, Y = Severity)
KEBA Industrial Automation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KUKA (X = Date, Y = Severity)
KUKA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

KEBA Industrial Automation

KUKA
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.