Comparison Overview
Oregon Audits Division
Oregon Audits Division
255 Capital Street NE, Salem, 97310, US
Last Update: 27/02/2026
The Oregon Audits Division is a division of the Oregon Secretary of State's Office. The division exists to fulfill the Secretary’s constitutional and statutory audit authority. We do this by auditing to protect the public interest and improve Oregon government. Our vis...
Workingfor.be
Simon Bolivarlaan 30, Brussels, 1000, BE
Last Update: 01/04/2026
Workingfor.be is the job platform of the federal administration. Here, you will find a wide variety of jobs in different fields of profession. Every day thousands of our employees help build tomorrow's society. When you choose the federal administration, you choos...
Compliance Ranges Comparison
Oregon Audits Division
Workingfor.be
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Oregon Audits Division in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Workingfor.be in 2026.
Incident History - Oregon Audits Division (X = Date, Y = Severity)
Oregon Audits Division cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Workingfor.be (X = Date, Y = Severity)
Workingfor.be cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Oregon Audits Division
Workingfor.be
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: *.*.