Comparison Overview
JLL UK
JLL UK
30 Warwick Street, London, W1B 5NH, GB
Last Update: 14/02/2026
JLL UK, a leading professional services firm specialising in real estate and investment management. We take pride in choosing the more intelligent, optimistic, and collaborative way forward. With over 200 years of real estate experience, we are,and always have been, in ...
Lopes Consultoria de Imóveis
Rua Estados Unidos, 1971, São Paulo, 01427-002, BR
Last Update: 01/04/2026
A GARANTIA DE SER LOPES A Lopes é a maior empresa de soluções integradas de intermediação, consultoria e promoção de financiamentos de imóveis do Brasil. Está presente em 10 estados - São Paulo, Rio de Janeiro, Minas Gerais, Espírito Santo, Rio Grande do Sul, Para...
Compliance Ranges Comparison
JLL UK
Lopes Consultoria de Imóveis
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for JLL UK in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Lopes Consultoria de Imóveis in 2026.
Incident History - JLL UK (X = Date, Y = Severity)
JLL UK cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lopes Consultoria de Imóveis (X = Date, Y = Severity)
Lopes Consultoria de Imóveis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
JLL UK
Lopes Consultoria de Imóveis
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: *.*.