Comparison Overview
R'Healthy Campus
R'Healthy Campus
900 University Ave, Riverside, California, US, 92507
Last Update: 01/04/2026
In April 1, 2024, the University of California, Riverside (UCR) adopted the Okanagan Charter, an initiative designed to provide universities with a common language, principle, and framework to promote health and well-being campuses UCR HC strives to make the healthy cho...
University of Waterloo
200 University Avenue West, Waterloo, N2L 3G1, CA
Last Update: 01/04/2026
University of Waterloo is a leader in innovation that drives economic and social prosperity for Canada and the world. We are home to a renowned talent pipeline, game-changing research and technology, and unmatched entrepreneurial culture, that together create solutions ...
Compliance Ranges Comparison
R'Healthy Campus
University of Waterloo
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for R'Healthy Campus in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Waterloo in 2026.
Incident History - R'Healthy Campus (X = Date, Y = Severity)
R'Healthy Campus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Waterloo (X = Date, Y = Severity)
University of Waterloo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
R'Healthy Campus
University of Waterloo
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.