Comparison Overview
University of Connecticut

University of Connecticut
352 Mansfield Road, Storrs, CT, US, 06269
Last Update: 13/09/2026
The University of Connecticut (UConn), a Wall Street Journal top 10 public university, is home to more than 32,000 students, 1,500 faculty, 255,000 proud alumni, and a handsome husky named Jonathan. The University has fourteen schools and colleges: Agriculture and Natu...

San José State University
1 Washington Square, San Jose, CA, US, 95192
Last Update: 12/09/2026
San José State University is a major, comprehensive public university located in Silicon Valley. The founding campus of the California State University system, SJSU takes pride in a faculty and student body that is active in hands-on learning, research, community servic...
Compliance Ranges Comparison

University of Connecticut







San José State University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Connecticut in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for San José State University in 2026.
Incident History - University of Connecticut (X = Date, Y = Severity)
University of Connecticut cyber incidents detection timeline including parent company and subsidiaries.
Incident History - San José State University (X = Date, Y = Severity)
San José State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

University of Connecticut

San José State University
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout