Comparison Overview
P2 Energy Services, LLC
P2 Energy Services, LLC
480 Wildwood Forest Dr, Spring, 77380, US
Last Update: 31/03/2026
As a leading supply chain solutions provider, P2 Energy Services helps operators navigate an ever-changing energy landscape. We’re a team of supply chain professionals, data-driven forecasters and sustainable product suppliers who support our customers with a blend of d...
Hindustan Petroleum Corporation Limited
IN
Last Update: 14/09/2026
Hindustan Petroleum Corporation Limited (HPCL) is a Maharatna Central Public Sector Enterprise (CPSE) and a S&P Global Platts Top 250 Global Energy Company. HPCL has a strong presence in downstream hydrocarbon sector of the country with a sizable share in petroleum prod...
Compliance Ranges Comparison
P2 Energy Services, LLC
Hindustan Petroleum Corporation Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for P2 Energy Services, LLC in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Hindustan Petroleum Corporation Limited in 2026.
Incident History - P2 Energy Services, LLC (X = Date, Y = Severity)
P2 Energy Services, LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hindustan Petroleum Corporation Limited (X = Date, Y = Severity)
Hindustan Petroleum Corporation Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
P2 Energy Services, LLC
Hindustan Petroleum Corporation Limited
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.