Comparison Overview
U.S. Embassy in Finland

U.S. Embassy in Finland
Itäinen Puistotie 14 B, Helsinki, 00140, FI
Last Update: 30/03/2026
U.S. Embassy Helsinki represents the government of the United States in Finland, advocates for U.S. interests in Finland to make America safer, stronger, and more prosperous, and supports the U.S. – Finland bilateral relationship. U.S. Department of State Social Media ...

UNDP
1 United Nations Plaza, New York, 10017, US
Last Update: 01/04/2026
The United Nations Development Programme works in nearly 170 countries and territories, helping to achieve the eradication of poverty, and the reduction of inequalities and exclusion. We help countries to develop policies, leadership skills, partnering abilities, instit...
Compliance Ranges Comparison

U.S. Embassy in Finland







UNDP






Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for U.S. Embassy in Finland in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for UNDP in 2026.
Incident History - U.S. Embassy in Finland (X = Date, Y = Severity)
U.S. Embassy in Finland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UNDP (X = Date, Y = Severity)
UNDP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Embassy in Finland

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