Comparison Overview
Zingat.com
Zingat.com
Ahi Evran Caddesi, Sariyer, Istanbul, 34485, TR
Last Update: 27/02/2026
Hakkımızda REIDIN ve Doğuş Grubu işbirliğiyle 2015 yılında faaliyete geçen Zingat, kaliteli hizmet ve şeffaf bilgi anlayışını benimseyerek gayrimenkul profesyonellerini ve bireyleri doğru, kapsamlı referans bilgilerle aynı çatı altında buluşturan güvenilir bir gayrimen...
JLL
200 East Randolph Drive, Chicago, Illinois, US, 60601
Last Update: 05/04/2026
We’re a leading professional services firm that specializes in real estate and investment management. JLL shapes the future of real estate for a better world by using the most advanced technology to create rewarding opportunities, amazing spaces and sustainable real est...
Compliance Ranges Comparison
Zingat.com
JLL
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Zingat.com in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for JLL in 2026.
Incident History - Zingat.com (X = Date, Y = Severity)
Zingat.com cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JLL (X = Date, Y = Severity)
JLL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Zingat.com
JLL
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: *.*.