Comparison Overview
Western Security Bank

Western Security Bank
2401 Grand Avenue FL 4, Billings, Montana, 59101, US
Last Update: 01/03/2026
Western Security Bank is a full service, community focused organization serving those who live and work in Yellowstone County, Montana. With conveniently located branches from Laurel to Lockwood, we offer more locations than any other financial institution serving the B...

OTP Group
Nádor u., Budapest, 1051, HU
Last Update: 18/09/2026
OTP Group is one of the fastest growing, leading independent banking groups in Central and Eastern Europe with a bridgehead in Central Asia. It operates in 11 countries - 10 in CEE region and 1 in Uzbekistan, employing nearly 40,000 people and providing universal finan...
Compliance Ranges Comparison

Western Security Bank







OTP Group






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

Western Security Bank

OTP 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.