Comparison Overview
Sasol em Moçambique

Sasol em Moçambique
833 Prédio Jat, Rua dos Desportistas, 833 , Maputo, Maputo , MZ, 1100
Last Update: 26/04/2026
Inspired by Mozambique and Mozambicans, we strive to ensure that the country’s hydrocarbon resources benefit all its people.

ConocoPhillips
925 N Eldridge Pkwy, Houston, 77079, US
Last Update: 12/09/2026
We are a global oil and gas company tasked with an important job—to safely find and deliver energy for the world. We’re experts in what we do—from the well site to the office. Across our operations and activities in 13 countries, we never forget our responsibility to ...
Compliance Ranges Comparison

Sasol em Moçambique







ConocoPhillips






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Sasol em Moçambique in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ConocoPhillips in 2026.
Incident History - Sasol em Moçambique (X = Date, Y = Severity)
Sasol em Moçambique cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ConocoPhillips (X = Date, Y = Severity)
ConocoPhillips cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sasol em Moçambique

ConocoPhillips
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.