Comparison Overview
SEMI Sustainability

SEMI Sustainability
Milpitas, 95035, US
Last Update: 04/04/2026
The Initiative brings members together from across the value chain to find solutions to common issues and share best practices. The power and speed of the Initiative comes from dividing and conquering along thematic lines and focusing on specific challenges to address....

Micron Technology
8000 S Federal Way, Boise, Idaho, US, 83706
Last Update: 12/07/2026
Micron is an industry leader in innovative memory and storage solutions transforming how the world uses information to enrich life for all. With a relentless focus on our customers, technology leadership, and manufacturing and operational excellence, Micron delivers a r...
Compliance Ranges Comparison

SEMI Sustainability







Micron Technology






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for SEMI Sustainability in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Micron Technology in 2026.
Incident History - SEMI Sustainability (X = Date, Y = Severity)
SEMI Sustainability cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Micron Technology (X = Date, Y = Severity)
Micron Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SEMI Sustainability

Micron Technology
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.