Comparison Overview
Technology Commercialization Office of the George Washington University
Technology Commercialization Office of the George Washington University
1922 F ST NW, 4TH FL, Washington, DC, 20052, US
Last Update: 24/02/2026
The George Washington University (GW) Technology Commercialization Office (TCO), promotes and facilitates the transfer of GW innovations for the benefit of the university community and the public while leveraging GW resources by partnering with industry experts and entr...
Yale University
Woodbridge Hall, New Haven, CT, US, 6520
Last Update: 08/05/2026
For more than 300 years, Yale University has inspired the minds that inspire the world. Based in New Haven, Connecticut, Yale brings people and ideas together for positive impact around the globe. A research university that focuses on students and encourages learning as...
Compliance Ranges Comparison
Technology Commercialization Office of the George Washington University
Yale University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Technology Commercialization Office of the George Washington University in 2026.
Incidents vs Higher Education Industry Avg (This Year)
Yale University has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Technology Commercialization Office of the George Washington University (X = Date, Y = Severity)
Technology Commercialization Office of the George Washington University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Yale University (X = Date, Y = Severity)
Yale University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Technology Commercialization Office of the George Washington University
Yale University
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.