Comparison Overview
GE
GE
41 Farnsworth St, Boston, 02210, US
Last Update: 16/08/2026
A new era is here, and we want you to be a part of it. We will now be sharing our content on our respective GE Aerospace and GE Vernova pages. Be sure to follow each to keep up with the future of aviation and energy.
SKF Group
Sven Wingquist Gata 2, Göteborg, SE-415 50, SE
Last Update: 23/09/2026
We fight friction to move the world forward. 20% of all energy consumed is spent overcoming friction. At SKF, we’re constantly fighting that friction, to reduce energy waste and make the most of the resources we have. Since 1907, we’ve been making some of the world’...
Compliance Ranges Comparison
GE
SKF Group
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for GE in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for SKF Group in 2026.
Incident History - GE (X = Date, Y = Severity)
GE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SKF Group (X = Date, Y = Severity)
SKF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
GE
SKF Group
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.