Comparison Overview
Semikron Danfoss

Semikron Danfoss
Sigmundstraße 200, Nuremberg, Bavaria, DE, 90431
Last Update: 24/03/2026
In a world that is going electric, Semikron Danfoss technologies are more relevant than ever. With our innovative solutions for automotive, industrial and renewable applications we help the world utilize energy more efficiently and sustainably and thus to significantly ...

AMD
2485 Augustine Drive, Santa Clara, 95054, US
Last Update: 05/10/2026
We care deeply about transforming lives with AMD technology to enrich our industry, our communities, and the world. Our mission is to build great products that accelerate next-generation computing experiences – the building blocks for the data center, artificial intelli...
Compliance Ranges Comparison

Semikron Danfoss







AMD






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Semikron Danfoss in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
AMD has 296.04% more incidents than the average of all companies with at least one recorded incident.
Incident History - Semikron Danfoss (X = Date, Y = Severity)
Semikron Danfoss cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AMD (X = Date, Y = Severity)
AMD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Semikron Danfoss

AMD
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.