Comparison Overview
Sequent Energy Management
Sequent Energy Management
1200 Smith St, Houston, Texas, 77002, US
Last Update: 01/04/2026
Williams completed its acquisition of Sequent Energy Management, L.P. and Sequent Energy Canada, Corp. from Southern Company Gas on July 1, 2021. The acquisition accelerates Williams’ natural gas pipeline and storage optimization and marketing growth and increases Will...
NOV
10353 Richmond Ave, Houston, Texas, US, 77042
Last Update: 17/09/2026
NOV delivers technology-driven solutions to empower the global energy industry. For more than 150 years, NOV has pioneered innovations that enable its customers to safely produce abundant energy while minimizing environmental impact. The energy industry depends on NOV’s...
Compliance Ranges Comparison
Sequent Energy Management
NOV
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Sequent Energy Management in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for NOV in 2026.
Incident History - Sequent Energy Management (X = Date, Y = Severity)
Sequent Energy Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NOV (X = Date, Y = Severity)
NOV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sequent Energy Management
NOV
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.