Comparison Overview
Wappa Brasil
Wappa Brasil
Avenida Faria Lima, São Paulo, São Paulo, BR, 01451-905
Last Update: 04/04/2026
A Wappa® é pioneira e líder no mercado de pagamentos e gerenciamento de despesas através do celular para clientes corporativos, possuindo uma carteira com mais de 300 Empresas-Clientes em todo o Brasil. A Wappa®, através do Sistema Wappa® Táxi, proporciona às empres...
Verzani & Sandrini
Rua Marina, 487, São Paulo, São Paulo, 09070-510, BR
Last Update: 01/04/2026
Com uma história sólida de sucesso desde sua fundação em 1967, a Verzani & Sandrini se destaca como líder nacional em diversos serviços terceirizados. Presente em todo o Brasil com mais de 71 mil colaboradores, atendemos setores como shopping centers, indústrias, hospi...
Compliance Ranges Comparison
Wappa Brasil
Verzani & Sandrini
Benchmark & Cyber Underwriting Signals
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Wappa Brasil in 2026.
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Verzani & Sandrini in 2026.
Incident History - Wappa Brasil (X = Date, Y = Severity)
Wappa Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Verzani & Sandrini (X = Date, Y = Severity)
Verzani & Sandrini cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wappa Brasil
Verzani & Sandrini
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: *.*.