Comparison Overview
CX Utilities Ltd (An RSK Company)

CX Utilities Ltd (An RSK Company)
Unit A9, Moorside Business Park, Moorside, Colchester, CO1 2ZF, GB
Last Update: 20/01/2026
For over 30 years our team have been at the forefront of the Utilities and Construction industry, working within both the private and public sectors, including: • Residential • Healthcare • Heritage Sites • Commercial Buildings • Education CX Utilities recognises the...

British Gas
Maidenhead Road, Windsor, GB
Last Update: 13/09/2026
Taking care of things. At British Gas we’re always looking at new ways to save energy and money for our customers. Everything we do from our trusted engineers to helpful call centre agents, and innovative product owners to digital marketing specialists, is about provi...
Compliance Ranges Comparison

CX Utilities Ltd (An RSK Company)







British Gas






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for CX Utilities Ltd (An RSK Company) in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for British Gas in 2026.
Incident History - CX Utilities Ltd (An RSK Company) (X = Date, Y = Severity)
CX Utilities Ltd (An RSK Company) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - British Gas (X = Date, Y = Severity)
British Gas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CX Utilities Ltd (An RSK Company)

British Gas
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.