Comparison Overview
San Francisco State University Development
San Francisco State University Development
1600 Holloway Ave, ADM153, San Francisco, California, US, 94132
Last Update: 20/02/2026
University Development is the fundraising arm of San Francisco State University. Funds raised from private individuals, organizations, businesses and foundations support students and faculty, ensuring an equitable and quality education for all of our students. Simply e...
UCLA
405 Hilgard Ave, Los Angeles, CA, US, 90095-1405
Last Update: 02/04/2026
UCLA offers a combination that’s rare, especially among public research universities. The breadth, depth and inspired excellence among academic programs—from the visual and performing arts to the humanities, social sciences, STEM disciplines and health sciences—add up t...
Compliance Ranges Comparison
San Francisco State University Development
UCLA
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for San Francisco State University Development in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for UCLA in 2026.
Incident History - San Francisco State University Development (X = Date, Y = Severity)
San Francisco State University Development cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UCLA (X = Date, Y = Severity)
UCLA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
San Francisco State University Development
UCLA
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: *.*.