Comparison Overview
THERMAX CONSTRUCTION LIMITED

THERMAX CONSTRUCTION LIMITED
SPRING COURT SPRING ROAD HALE, ALTRINCHAM, CHESHIRE, GB, WA14 2UQ
Last Update: 07/08/2026

Kiewit
1550 Mike Fahey St., Omaha, 68102, US
Last Update: 15/09/2026
At Kiewit, the projects we deliver make a difference, and we offer opportunities for you to make one, too. Our construction and engineering professionals work on some of the industry’s most complex, challenging and rewarding projects – whether it’s boring tunnels throug...
Compliance Ranges Comparison

THERMAX CONSTRUCTION LIMITED







Kiewit






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for THERMAX CONSTRUCTION LIMITED in 2026.
Incidents vs Construction Industry Avg (This Year)
Kiewit has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - THERMAX CONSTRUCTION LIMITED (X = Date, Y = Severity)
THERMAX CONSTRUCTION LIMITED cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kiewit (X = Date, Y = Severity)
Kiewit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

THERMAX CONSTRUCTION LIMITED

Kiewit
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.