Comparison Overview
UOB

UOB
80 Raffles Place, Singapore, 048624, SG
Last Update: 28/03/2026
We’re here to do Right By You. At UOB, we aspire to build a better future for the people and businesses in the region. Through our extensive network and suite of capabilities, we offer financial solutions to the people and businesses within, and connecting with ASE...

Federal Bank
Federal Towers, Head Office, Ernakulam, 683101, IN
Last Update: 14/09/2026
Federal Bank, one of the leading private sector banks with presence across the country, began its journey from humble backgrounds to reach the stature of an institution with national prominence & character. With a rich legacy of 7 decades, the Bank aspires to be the mos...
Compliance Ranges Comparison

UOB







Federal Bank






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

UOB

Federal Bank
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.