Comparison Overview
Oakbrook

Oakbrook
The Poynt North, Nottingham, undefined, NG1 5FW, GB
Last Update: 15/03/2026
Oakbrook is a digitally enabled consumer finance and technology business, removing the barriers between consumers that want to borrow and investors that want to lend. Formed in 2011, Oakbrook has brought together people with deep expertise in consumer lending, advanced...

Merrill Lynch
2 World Financial Center, New York, 10281, US
Last Update: 13/09/2026
Founded in 1914, Merrill is one of the largest wealth management businesses in the world. Merrill financial advisors combine financial knowledge and experience with a deep understanding of their clients’ needs to help their clients pursue the lives they want. With a dee...
Compliance Ranges Comparison

Oakbrook







Merrill Lynch






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

Oakbrook

Merrill Lynch
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.