Comparison Overview
Goldman Sachs Transaction Banking

Goldman Sachs Transaction Banking
New York, US
Last Update: 16/02/2026
Goldman Sachs Transaction Banking is helping clients build a treasury of the future and powering software partners to enhance their offerings. Our mission is simple: to provide a global transaction banking platform that is nimble, secure, and easy for clients to use and...

Equifax
P.O. Box 740241, Atlanta, 30374, US
Last Update: 14/10/2026
At Equifax (NYSE: EFX), we believe knowledge drives progress. As a global data, analytics, and technology company, we play an essential role in the global economy by helping financial institutions, companies, employers, and government agencies make critical decisions wi...
Compliance Ranges Comparison

Goldman Sachs Transaction Banking







Equifax






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Goldman Sachs Transaction Banking in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Equifax has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Goldman Sachs Transaction Banking (X = Date, Y = Severity)
Goldman Sachs Transaction Banking cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Equifax (X = Date, Y = Severity)
Equifax cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Goldman Sachs Transaction Banking

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