Comparison Overview
TD Enterprise Real Estate

TD Enterprise Real Estate
undefined, Toronto, Ontario, M5K 1A2, CA
Last Update: 19/04/2026
The Enterprise Real Estate team is a proactive strategic business partner and helps build TD from the ground up—literally. We play an active role, working with TD's lines of business, HR and Technology to understand business goals and create the future vision for space...

DNB
Dronning Eufemias gate 30, Oslo, 0191, NO
Last Update: 12/09/2026
We are here. So you can stay ahead. For nearly two hundred years we have acquired and shared knowledge, developed global networks and adapted to modern everyday life. To us, it is important to combine profitability with responsibility. DNB is Norway's largest financi...
Compliance Ranges Comparison

TD Enterprise Real Estate







DNB






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

TD Enterprise Real Estate

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