Comparison Overview
BI Incorporated
BI Incorporated
6265 Gunbarrel Avenue, Suite B, Boulder, 80301, US
Last Update: 30/01/2026
Established in 1978, BI Incorporated offers government agencies a complete continuum of electronic monitoring technologies and services for reliable community supervision of individuals on parole, probation, and pretrial release, and individuals involved in the U.S. imm...
TÜV SÜD
Westendstr. 199, Munich, Germany, DE, 80686
Last Update: 01/04/2026
TÜV SÜD is the trusted partner of choice for safety, security and sustainability solutions. Our community of experts is passionate about technology and united by the belief that technology should better people’s lives. We work alongside our customers to anticipate and...
Compliance Ranges Comparison
BI Incorporated
TÜV SÜD
Benchmark & Cyber Underwriting Signals
Incidents vs Public Safety Industry Avg (This Year)
No incidents recorded for BI Incorporated in 2026.
Incidents vs Public Safety Industry Avg (This Year)
No incidents recorded for TÜV SÜD in 2026.
Incident History - BI Incorporated (X = Date, Y = Severity)
BI Incorporated cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TÜV SÜD (X = Date, Y = Severity)
TÜV SÜD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BI Incorporated
TÜV SÜD
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.