Comparison Overview
IPG Mediabrands Colombia

IPG Mediabrands Colombia
Calle 100 No 7ª – 81 Piso 4 - 5, Bogotá, Bogotá D.C., 110221, CO
Last Update: 18/02/2026
MEDIABRANDS, es un grupo de agencias alrededor del mundo, diseñadas con el marketing dinámico en su núcleo. Somos 8,500 especialistas de comunicación de marketing, medios de comunicación y la tecnología en más de 130 países. Somos un grupo diverso de innovadores, tecn...

Epsilon
6021 Connection Drive, Irving, Texas, US, 75039
Last Update: 15/09/2026
Epsilon is a global data, technology and services company that powers the marketing and advertising ecosystem. The world’s leading brands use Epsilon to harmonize consumer engagement across their paid, owned and earned channels, leveraging capabilities that include da...
Compliance Ranges Comparison

IPG Mediabrands Colombia







Epsilon






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

IPG Mediabrands Colombia

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