Comparison Overview
OP Labs PBC
OP Labs PBC
Remote first, Worldwide, US
Last Update: 01/04/2026
OP Labs is the team building the technology that powers Optimism, the leading blockchain infrastructure provider enabling developers and enterprises to build the next generation of onchain applications. Our open-source OP Stack delivers Ethereum-grade security, fast tr...
Red Hat
100 E. Davie St., Raleigh, NC, US, 27601
Last Update: 15/09/2026
Red Hat is the world’s leading provider of enterprise open source solutions, using a community-powered approach to deliver high-performing Linux, hybrid cloud, edge, and Kubernetes technologies. We hire creative, passionate people who are ready to contribute their idea...
Compliance Ranges Comparison
OP Labs PBC
Red Hat
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
OP Labs PBC has 5.66% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Red Hat in 2026.
Incident History - OP Labs PBC (X = Date, Y = Severity)
OP Labs PBC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Red Hat (X = Date, Y = Severity)
Red Hat cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OP Labs PBC
Red Hat
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.