Comparison Overview
Chevron

Chevron
1400 Smith St, Houston, Texas, US, 77002
Last Update: 05/09/2026
Our greatest resource is our people. Their ingenuity, creativity and collaboration have met the complex challenges of energy’s past. Together, we’ll take on the future. We support the LinkedIn Terms of Use (User Agreement), and we expect visitors to our page to do the ...

Tenaris
2200 West Loop South, Suite 800, Houston, 77027, US
Last Update: 18/09/2026
Tenaris is a leading supplier of tubes and related services for the world’s energy industry and certain other industrial applications. Our mission is to deliver value to our customers through product development, manufacturing excellence, and supply chain management. Te...
Compliance Ranges Comparison

Chevron







Tenaris






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
Chevron has 56.9% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Tenaris in 2026.
Incident History - Chevron (X = Date, Y = Severity)
Chevron cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tenaris (X = Date, Y = Severity)
Tenaris cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chevron

Tenaris
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).