Comparison Overview
Brigham Young University
Brigham Young University
Main Campus, Provo, UT, US, 84602
Last Update: 02/04/2026
We believe a world yearning for hope and joy needs the graduates of Brigham Young University—disciples of Jesus Christ who are driven by love for God and His children and who are prepared to serve and lead. This preparation demands a unique university model: at BYU, bel...
The George Washington University
2121 I Street, NW, Washington, D.C., US, 20052
Last Update: 02/04/2026
The George Washington University, an independent academic institution chartered by the Congress of the United States in 1821, dedicates itself to furthering human well-being. The University values a dynamic, student-focused community stimulated by cultural and intellect...
Compliance Ranges Comparison
Brigham Young University
The George Washington University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Brigham Young University in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The George Washington University in 2026.
Incident History - Brigham Young University (X = Date, Y = Severity)
Brigham Young University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The George Washington University (X = Date, Y = Severity)
The George Washington University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brigham Young University
The George Washington University
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: *.*.