Comparison Overview
Regulatory Reporting

Regulatory Reporting
10 Paternoster Square, London, undefined, EC4M 7LS, GB
Last Update: 01/03/2026
LSEG Post Trade is reframing regulatory reporting through data insights, workflow automation and easy onboarding. Our innovative solutions allow firms to reduce their regulatory risk, free up resources by increasing operational efficiencies, and derive greater value fr...

Discover
2500 Lake Cook Road, Riverwoods, IL, US, 60015
Last Update: 16/09/2026
Discover® is now part of Capital One. Together, we’ll continue to deliver exceptional financial products and experiences, drive innovation, and serve customers. Find the latest updates at https://capitalonediscover.com. Discover is one of the most recognized brands in ...
Compliance Ranges Comparison

Regulatory Reporting







Discover






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

Regulatory Reporting

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