Comparison Overview
Taylor Promo Marketing

Taylor Promo Marketing
1725 Roe Crest Dr, North Mankato, 56003, US
Last Update: 06/01/2026
Explore how Taylor Communications can improve your promotional marketing effectiveness and efficiency. Now you can leverage the benefits of working with one of the largest distributors of promotional marketing in North America without sacrificing the convenience of a d...

Havas
29/30 Quai de Dion Bouton, Puteaux, FR, 92800
Last Update: 04/04/2026
Founded in 1835 in Paris, Havas is one of the world’s largest global communications groups, with nearly 23,000 people in over 100 countries. With the ambition to help brands unlock Growth, Powered by Desire, Havas brings together creativity, media, technology and produc...
Compliance Ranges Comparison

Taylor Promo Marketing







Havas






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

Taylor Promo Marketing

Havas
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: *.*.