Comparison Overview
JLL Germany
JLL Germany
Bockenheimer Landstraße 55, Frankfurt, 60325, DE
Last Update: 14/02/2026
Wir sind ein führendes Unternehmen im Bereich professioneller Dienstleistungen, das sich auf Immobilien- und Investmentmanagement spezialisiert hat. JLL gestaltet die Zukunft der Immobilienbranche für eine bessere Welt, indem wir die fortschrittlichste Technologie einse...
Emaar
Emaar Square Downtown Dubai, Dubai, 9440, AE
Last Update: 07/05/2026
WHO WE ARE Emaar is a pioneer of master-planned communities in Dubai since its inception in 1997. It is listed on the Dubai Financial Market as a public joint-stock company. Building upon the legacy of our flagship Downtown Dubai creations — the iconic Burj Khalifa, Du...
Compliance Ranges Comparison
JLL Germany
Emaar
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for JLL Germany in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Emaar in 2026.
Incident History - JLL Germany (X = Date, Y = Severity)
JLL Germany cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Emaar (X = Date, Y = Severity)
Emaar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
JLL Germany
Emaar
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: *.*.