Comparison Overview
Zorg van Nu
Zorg van Nu
Den Haag, NL
Last Update: 11/06/2026
Er komen steeds meer nieuwe en digitale toepassingen voor gezondheid en zorg, maar deze worden nog weinig gebruikt. Daarom laten we met Zorg van Nu zien wat er allemaal mogelijk is op het gebied van e-health, zorginnovaties en nieuwe hulpmiddelen. Slimme zorg is ‘zorg v...
State of Oregon
Salem, 97301, US
Last Update: 01/04/2026
Official LinkedIn page for the state of Oregon. Oregon is a state in the Pacific Northwest region of the United States. It is located on the Pacific coast, with Washington to the north, California to the south, Nevada on the southeast and Idaho to the east. The Columbia...
Compliance Ranges Comparison
Zorg van Nu
State of Oregon
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Zorg van Nu in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State of Oregon in 2026.
Incident History - Zorg van Nu (X = Date, Y = Severity)
Zorg van Nu cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Oregon (X = Date, Y = Severity)
State of Oregon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Zorg van Nu
State of Oregon
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: *.*.