Comparison Overview
Prefeitura do Município de São Bernardo do Campo

Prefeitura do Município de São Bernardo do Campo
N/A
Last Update: 05/12/2025

South African Revenue Service (SARS)
Lehae La Sars, Pretoria, 0001, ZA
Last Update: 29/03/2026
Its main functions are to: collect and administer all national taxes, duties and levies; collect revenue that may be imposed under any other legislation, as agreed on between SARS and an organ of state or institution entitled to the revenue; provide protection a...
Compliance Ranges Comparison

Prefeitura do Município de São Bernardo do Campo







South African Revenue Service (SARS)






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Prefeitura do Município de São Bernardo do Campo in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for South African Revenue Service (SARS) in 2026.
Incident History - Prefeitura do Município de São Bernardo do Campo (X = Date, Y = Severity)
Prefeitura do Município de São Bernardo do Campo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - South African Revenue Service (SARS) (X = Date, Y = Severity)
South African Revenue Service (SARS) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prefeitura do Município de São Bernardo do Campo

South African Revenue Service (SARS)
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: *.*.