Comparison Overview
Leybold

Leybold
Bonner Straße 498, Cologne, North Rhine-Westphalia, undefined, DE
Last Update: 07/03/2026
We have been delivering vacuum pumps, systems, accessories, services and tailor-made vacuum solutions for almost 170 years. At Leybold we enable precise, innovative, economical and sustainable manufacturing of vacuum solutions and services. We offer a broad range of a...

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

Leybold







AGCO Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Leybold in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for AGCO Corporation in 2026.
Incident History - Leybold (X = Date, Y = Severity)
Leybold 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

Leybold

AGCO Corporation
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.