Comparison Overview
DEVA Bearings
DEVA Bearings
Schulstr. 20, Stadtallendorf, 35260 , DE
Last Update: 08/03/2026
For over 85 years, maintenance-free, self-lubricating sliding bearings from DEVA have been proving themselves in innumerable industrial applications. Our products can be found in large machines, in the construction and automotive industries, in wind turbines and hydroe...
AGCO Corporation
4205 River Green Parkway, Duluth, Georgia, US, 30096
Last Update: 02/04/2026
AGCO (NYSE: AGCO) is a global leader in the design, manufacture and distribution of agricultural machinery and precision ag technology. AGCO delivers value to farmers and OEM customers through its differentiated brand portfolio including leading brands Fendt®, Massey Fe...
Compliance Ranges Comparison
DEVA Bearings
AGCO Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for DEVA Bearings in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for AGCO Corporation in 2026.
Incident History - DEVA Bearings (X = Date, Y = Severity)
DEVA Bearings cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AGCO Corporation (X = Date, Y = Severity)
AGCO Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DEVA Bearings
AGCO Corporation
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.