Comparison Overview
Texas Tech University - Rawls College of Business

Texas Tech University - Rawls College of Business
703 Flint Avenue, Lubbock, 79409, US
Last Update: 04/04/2026
The Jerry S. Rawls College of Business is home to challenge seekers venturing to change the business world through research, innovation and determination. Founded in 1942 and originally known as the Division of Commerce, the college has grown exponentially over the las...

Stanford University
450 Jane Stanford Way, Stanford, CA, US, 94305
Last Update: 08/05/2026
Stanford is a place of discovery, creativity and innovation located in the San Francisco Bay Area on the ancestral land of the Muwekma Ohlone Tribe. Dedicated to our founding mission—benefitting society through research and education—we are working toward a sustainable ...
Compliance Ranges Comparison

Texas Tech University - Rawls College of Business







Stanford University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Texas Tech University - Rawls College of Business in 2026.
Incidents vs Higher Education Industry Avg (This Year)
Stanford University has 183.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Texas Tech University - Rawls College of Business (X = Date, Y = Severity)
Texas Tech University - Rawls College of Business cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Stanford University (X = Date, Y = Severity)
Stanford University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Texas Tech University - Rawls College of Business

Stanford University
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.