Comparison Overview
Capacity Building Center for States
Capacity Building Center for States
N/A
Last Update: 06/02/2026
The Capacity Building Center for States (the Center) partners with State and territorial public child welfare agencies to achieve better outcomes for children, youth, and families. Join our email community to stay in touch and in the know about what’s happening at the...
I WORK FOR SA
200, Victoria Square / Tarndanyangga, Adelaide, 5000, AU
Last Update: 01/04/2026
The OFFICIAL careers page for the South Australian Government. The South Australian Public Sector is the State's largest workforce. We are an employer of choice that reflects the diverse community we serve. Our people are from a range of backgrounds and vocations, fro...
Compliance Ranges Comparison
Capacity Building Center for States
I WORK FOR SA
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Capacity Building Center for States in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for I WORK FOR SA in 2026.
Incident History - Capacity Building Center for States (X = Date, Y = Severity)
Capacity Building Center for States cyber incidents detection timeline including parent company and subsidiaries.
Incident History - I WORK FOR SA (X = Date, Y = Severity)
I WORK FOR SA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Capacity Building Center for States
I WORK FOR SA
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: *.*.