Comparison Overview
Danske Bank Asset Management

Danske Bank Asset Management
Bernstorffsgade 40, Copenhagen, 1577, DK
Last Update: 10/03/2026
Danske Bank Asset Management is an international asset manager and part of Danske Bank A/S. We serve clients in the Nordics and around the world. Our headquarters is located in Denmark, but we also operate from offices in Sweden, Norway and Finland. Follow us for insi...

Odebrecht
Av. Luís Viana, 2841, Salvador, 41730-900, BR
Last Update: 18/09/2026
Founded in 1944, Odebrecht is a Brazilian group with diverse businesses and world-class standards of quality. Its Members, guided by the Group’s own philosophy, the Odebrecht Entrepreneurial Technology (TEO), provide services and manufacture products for clients on fiv...
Compliance Ranges Comparison

Danske Bank Asset Management







Odebrecht






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

Danske Bank Asset Management

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