Comparison Overview
Sprint

Sprint
6200 Sprint Pkwy, Overland Park, Kansas, US, 66251
Last Update: 28/09/2026
Thanks for everything! This account is no longer active. Follow us at T-Mobile For Business to learn more about the new T-Mobile® Business Advantage. https://www.linkedin.com/showcase/t-mobile-business/

Zain Group
Airport Road, P.O. Box 22244, Kuwait, KW
Last Update: 07/09/2026
Zain Group is a leading provider of innovative ICT technologies & digital lifestyle communications operating in 8 markets across the Middle East & Africa, serving 51.3 million active customers as of 30 September 2025. Zain provides mobile voice, data and B2B services in...
Compliance Ranges Comparison

Sprint







Zain Group






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

Sprint

Zain Group
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.