Comparison Overview
IPG Mediabrands Argentina
IPG Mediabrands Argentina
undefined, Ciudad de Buenos Aires, undefined, undefined, AR
Last Update: 08/03/2026
IPG Mediabrands es el grupo global de soluciones de marketing y medios de Interpublic Group (NYSE:IPG). En la actualidad la red emplea más de 12.000 especialistas en comunicación de marketing en más de 130 países. La amplia red de agencias globales e integrales de IPG ...
Publicis Groupe
133, avenue des Champs-Elysées, Paris, 75008, FR
Last Update: 07/05/2026
Founded in 1926 by Marcel Bleustein-Blanchet, today Publicis Groupe is the largest communications group in the world and a leader in marketing, communication, and digital business transformation, led by Arthur Sadoun, the third CEO in its history. Publicis Groupe is p...
Compliance Ranges Comparison
IPG Mediabrands Argentina
Publicis Groupe
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for IPG Mediabrands Argentina in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Publicis Groupe in 2026.
Incident History - IPG Mediabrands Argentina (X = Date, Y = Severity)
IPG Mediabrands Argentina cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Publicis Groupe (X = Date, Y = Severity)
Publicis Groupe cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
IPG Mediabrands Argentina
Publicis Groupe
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.