Comparison Overview
University of Nebraska System

University of Nebraska System
3835 Holdrege St, Lincoln, 68583, US
Last Update: 01/04/2026
This is the official LinkedIn page of the the University of Nebraska System, the state of Nebraska's only public university. The NU System is comprised of four campuses: the University of Nebraska-Lincoln, the University of Nebraska at Omaha, the University of Nebraska ...

Temple University
1801 N Broad St, Philadelphia, Pennsylvania, US, 19122
Last Update: 02/04/2026
As the largest university in one of the nation’s most iconic cities, Temple educates diverse future leaders from across Philadelphia, the country and the world who share a common drive to learn, prepare for their careers and make a real impact. Founded as a night school...
Compliance Ranges Comparison

University of Nebraska System







Temple University






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

University of Nebraska System

Temple University
FAQ
Latest Global CVEs
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/handler.go sendFile handler opened files using a cleaned path but derived the authorization filename from raw req.URL.Path, so a trailing slash could bypass .goshs ACL-file protection and block-list checks. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.
goshs is a feature-rich single-binary file server for red teamers and developers. From 2.1.3 until 2.1.4, the sftpserver/sftpserver.go password handler used Username != "" && Password != "", so running goshs with -b 'admin:' -sftp and no -fkf left both SFTP authentication handlers unset and allowed unauthenticated file access. This issue is fixed in version 2.1.4.
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.