Comparison Overview
City of Bend
City of Bend
710 NW Wall St, Bend, OR, US
Last Update: 31/03/2026
Official LinkedIn for the City of Bend, Oregon. Our city features breathtaking scenery, year-round outdoor activities and a population of nearly 103,000. To view and apply for current job opportunities, please visit: governmentjobs.com/careers/bend Watch our latest u...
US Environmental Protection Agency (EPA)
1200 Pennsylvania Ave. N.W., Washington, 20004, US
Last Update: 31/03/2026
U.S. Environmental Protection Agency’s (EPA) mission is to protect human health and the environment. EPA works to ensure that: - Americans have clean air, land and water; - National efforts to reduce environmental risks are based on the best available scientific inform...
Compliance Ranges Comparison
City of Bend
US Environmental Protection Agency (EPA)
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Bend in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for US Environmental Protection Agency (EPA) in 2026.
Incident History - City of Bend (X = Date, Y = Severity)
City of Bend cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Environmental Protection Agency (EPA) (X = Date, Y = Severity)
US Environmental Protection Agency (EPA) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
City of Bend
US Environmental Protection Agency (EPA)
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: *.*.