Comparison Overview
T3 Micro Inc

T3 Micro Inc
880 Apollo St, None, El Segundo, California, US, 90245
Last Update: 04/04/2026
Hair is a powerful thing. It’s the ultimate accessory. An expression of personal style that’s uniquely yours. At T3, we create innovative styling tools and content that demystify your styling routine and put you in control. From heat technology that understands your hai...

Kohler Co.
444 Highland Drive, Kohler, Wisconsin, US, 53044
Last Update: 03/04/2026
We’re a community of creators. Status quo busters. Difference makers. For more than 150 years, we’ve built our business on a singular mission—helping people live gracious, healthy, and sustainable lives. Thanks to the passion, craftsmanship, and ingenuity of our ass...
Compliance Ranges Comparison

T3 Micro Inc







Kohler Co.






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for T3 Micro Inc in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kohler Co. in 2026.
Incident History - T3 Micro Inc (X = Date, Y = Severity)
T3 Micro Inc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kohler Co. (X = Date, Y = Severity)
Kohler Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

T3 Micro Inc

Kohler Co.
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.