Comparison Overview
Edenred Sweden

Edenred Sweden
Liljeholmsstranden 3, Stockholm, 117 43, SE
Last Update: 06/03/2026
Vi tror på öronmärkta må bra-medel. Att det får både människor och företag att växa. Därför ger vi dig som arbetsgivare möjlighet att erbjuda dina anställda bra och smarta förmåner. Förmåner som boostar hälsa och glädje. Som lyfter vardagen. Vi kallar det kort och gott ...

Discovery Limited
1 Discovery Place, Sandhurst, Johannesburg, Gauteng, ZA, 2196
Last Update: 01/04/2026
Imagine a world where people live healthier, more enhanced and protected lives… A world in which each organisation is a powerful influencer and responsible corporate citizen, committed to being a force for social good. As a leading innovator in healthcare, wellness, ins...
Compliance Ranges Comparison

Edenred Sweden







Discovery Limited






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

Edenred Sweden

Discovery Limited
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.