Comparison Overview

Asahi Kasei Microdevices (AKM)
1-1-2, Yurakucho, Chiyoda, JP
Last Update: 01/04/2026
Asahi Kasei Microdevices (AKM) offer a variety of advanced sensing devices based on compound semiconductor technology and sophisticated IC products featuring analog/digital mixed-signal technology. Additional information is available at www.akm.com Please use Inquiries...

Texas Instruments
12500 T I Blvd, Dallas, 75243, US
Last Update: 19/07/2026
We are a global semiconductor company that designs, manufactures and sells analog and embedded processing chips for markets such as industrial, automotive, personal electronics, enterprise systems and communications equipment. At our core, we have a passion to create a ...
Compliance Ranges Comparison
Asahi Kasei Microdevices (AKM)







Texas Instruments






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

Texas Instruments
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.