Comparison Overview
INEOS Aromatics

INEOS Aromatics
4201 Winfield Rd, Warrenville, 60555, US
Last Update: 13/01/2026
From soft drink bottles to packaging trays, from clothing to carpet, INEOS Aromatics makes the chemicals used to produce many of the things we use in our daily lives. INEOS Aromatics is a global leader in PTA (purified terephthalic acid) and PX (paraxylene) technology, ...

SABIC
PO Box 5101, Riyadh, SA, 11422
Last Update: 29/07/2026
SABIC is a global leader in chemicals headquartered in Riyadh, Saudi Arabia. From making cars and planes more fuel-efficient, to helping conserve the world’s water supply and enabling colorful smartphone cases, we find solutions to the challenges of today to help our cu...
Compliance Ranges Comparison

INEOS Aromatics







SABIC






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

INEOS Aromatics

SABIC
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.