Comparison Overview
Ogilvy Health Australia
Ogilvy Health Australia
The Bond, 30 Hickson Rd, Millers Point, New South Wales, AU, 2000
Last Update: 20/01/2026
Ogilvy Health are behaviour change experts for health and wellness with the simple aim to make a difference to our clients, their brands and ultimately the health of all people. Our tenacity, experience and partnerships deliver inspired creative and communications acro...
Epsilon
6021 Connection Drive, Irving, Texas, US, 75039
Last Update: 30/03/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
Ogilvy Health Australia
Epsilon
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Ogilvy Health Australia in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Epsilon in 2026.
Incident History - Ogilvy Health Australia (X = Date, Y = Severity)
Ogilvy Health Australia 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
Ogilvy Health Australia
Epsilon
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: *.*.