Comparison Overview
Amazon | Liquavista

Amazon | Liquavista
N/A
Last Update: 10/03/2026
Based in Eindhoven, the high-tech capital of The Netherlands, Liquavista is developing a revolutionary type of electronic display technology called “electrowetting” (EWD). Our electrowetting display technology will delight customers by having unsurpassed outdoor readabi...

Flex
12455 Research Blvd, Austin, Texas, US, 78759
Last Update: 04/04/2026
Flex (Reg. No. 199002645H) is the global manufacturing partner of choice that helps leading brands design, build, and manage products that improve the world. For more information, visit flex.com. We love to hear your thoughts, comments and ideas so feel free to like, s...
Compliance Ranges Comparison

Amazon | Liquavista







Flex






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Amazon | Liquavista in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Flex in 2026.
Incident History - Amazon | Liquavista (X = Date, Y = Severity)
Amazon | Liquavista cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Flex (X = Date, Y = Severity)
Flex cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amazon | Liquavista

Flex
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.