Comparison Overview
VINCI Immobilier Conseil
VINCI Immobilier Conseil
2313, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 19/12/2025
Parce que l’immobilier est au cœur de la stratégie des entreprises, VINCI Immobilier Conseil propose aux décideurs un accompagnement sur-mesure afin d’optimiser leur stratégie immobilière. Nous mettons toute notre expertise en œuvre pour offrir un service complet et in...
Savills
33 Margaret Street, London, GB, W1G 0JD
Last Update: 01/04/2026
Savills is a global real estate advisor helping people thrive through places and spaces. With over 42,000 professionals in more than 700 offices across the Americas, Europe, Asia Pacific, Africa and the Middle East, we combine local knowledge with global insight to del...
Compliance Ranges Comparison
VINCI Immobilier Conseil
Savills
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for VINCI Immobilier Conseil in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Savills in 2026.
Incident History - VINCI Immobilier Conseil (X = Date, Y = Severity)
VINCI Immobilier Conseil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Savills (X = Date, Y = Severity)
Savills cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VINCI Immobilier Conseil
Savills
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: *.*.