Comparison Overview
Scottish Widows Workplace Pensions

Scottish Widows Workplace Pensions
London, City of London, GB
Last Update: 19/02/2026
At Scottish Widows, we build long term relationships with employers and our relationship-led service teams can help employers and their employees; from setting up schemes to supporting the on-going management of workplace pension schemes. We can provide contract-based ...

Santander US
75 State Street, Boston, 02109, US
Last Update: 12/09/2026
Santander’s purpose is to help people and businesses prosper. In the United States, Santander is a leading financial services provider with approximately 11,000 employees, 4.3 million customers, and assets of $243 billion, as of Q4 2025. Our five diverse and growing bu...
Compliance Ranges Comparison

Scottish Widows Workplace Pensions







Santander US






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Scottish Widows Workplace Pensions in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Santander US in 2026.
Incident History - Scottish Widows Workplace Pensions (X = Date, Y = Severity)
Scottish Widows Workplace Pensions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Santander US (X = Date, Y = Severity)
Santander US cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Scottish Widows Workplace Pensions

Santander US
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.