Comparison Overview
Polygon Labs

Polygon Labs
39 W 38th St, New York, 10018, US
Last Update: 04/04/2026
Polygon Labs is a creative services and software solutions company focusing on engaging data and content visualization for the Media Industry. We design and develop some of the most engaging virtual collaboration, mixed reality, data visualization, and real-time graphic...

Siemens Digital Industries Software
5800 Granite Pkwy, 600, Plano, Texas, US, 75024
Last Update: 25/09/2026
We help organizations of all sizes digitally transform using software, hardware and services from the Siemens Xcelerator business platform. Our software and the comprehensive digital twin enable companies to optimize their design, engineering and manufacturing processes...
Compliance Ranges Comparison

Polygon Labs







Siemens Digital Industries Software






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Polygon Labs has 3.85% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Siemens Digital Industries Software has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Polygon Labs (X = Date, Y = Severity)
Polygon Labs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Siemens Digital Industries Software (X = Date, Y = Severity)
Siemens Digital Industries Software cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Polygon Labs

Siemens Digital Industries Software
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.