Comparison Overview
Christ Uhren & Schmuck

Christ Uhren & Schmuck
8401, CH
Last Update: 02/04/2026
Seit über 40 Jahren steht CHRIST für ausgezeichnete Qualität und besten Service in Sachen Uhren und Schmuck. Mit 60 Filialen und einem umfassenden und stetig erweiterten Angebot sind wir zur grössten Bijouterie-Kette der Schweiz herangewachsen. Unsere Kunden begrüssen w...

SWAROVSKI
Alte Landstrasse, 411, Männedorf, CH, 8708
Last Update: 01/04/2026
Masters of Light Since 1895 Swarovski creates beautiful products of impeccable quality and craftsmanship that bring joy and celebrate individuality. Founded in 1895 in Austria, the company designs, manufactures, and sells the world's finest crystals, Swarovski Created ...
Compliance Ranges Comparison

Christ Uhren & Schmuck







SWAROVSKI






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Christ Uhren & Schmuck in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for SWAROVSKI in 2026.
Incident History - Christ Uhren & Schmuck (X = Date, Y = Severity)
Christ Uhren & Schmuck cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SWAROVSKI (X = Date, Y = Severity)
SWAROVSKI cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Christ Uhren & Schmuck

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