Comparison Overview
Interface, Inc.

Interface, Inc.
7401 E Butherus Dr, None, Scottsdale, AZ, US, 85260
Last Update: 03/04/2026
We are the trusted world leader in force measurement solutions by designing, manufacturing, and guaranteeing the highest quality performance load cells, torque transducers, multi-axis sensors, and related instrumentation available in the market today. Whether you are do...

Xylem
301 Water St SE, Washington, District of Columbia, US, 20003
Last Update: 23/09/2026
Xylem is the global leader in advanced technologies, solutions and services that address the world’s biggest water challenges. We enable our customers to dramatically improve the way water and wastewater is used, managed, conserved, re-used and returned to nature. At e...
Compliance Ranges Comparison

Interface, Inc.







Xylem






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

Interface, Inc.

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