Comparison Overview
Everyday Health Group
Everyday Health Group
undefined, New York, NY, 10010, US
Last Update: 05/12/2025
The Everyday Health Group (EHG) is a recognized leader in patient and provider education and services attracting an engaged audience of over 74 million health consumers and over 890,000 U.S. practicing physicians and clinicians. Our mission is to drive better clinical a...
Equinix
One Lagoon Drive, Redwood City, 94065, US
Last Update: 08/07/2026
Equinix (Nasdaq: EQIX) is the world’s digital infrastructure company®, enabling digital leaders to harness a trusted platform to bring together and interconnect the foundational infrastructure that powers their success. Equinix enables today’s businesses to access all t...
Compliance Ranges Comparison
Everyday Health Group
Equinix
Benchmark & Cyber Underwriting Signals
Incidents vs Internet Publishing Industry Avg (This Year)
No incidents recorded for Everyday Health Group in 2026.
Incidents vs Internet Publishing Industry Avg (This Year)
Equinix has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Everyday Health Group (X = Date, Y = Severity)
Everyday Health Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Equinix (X = Date, Y = Severity)
Equinix cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Everyday Health Group
Equinix
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: *.*.