Comparison Overview

Weatherford

VS

Baker Hughes

Weatherford

undefined, Dublin, undefined, undefined, IE
Last Update: 2025-12-09
Between 750 and 799

Weatherford International plc (Nasdaq: WFRD) is a leading global energy services company. Operating in approximately 75 countries, the Company answers the challenges of the energy industry with its global talent network of approximately 17,000 team members and approximately 350 operating locations, including manufacturing, research and development, service, and training facilities.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 29,461
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Baker Hughes

17021 Aldine Westfield, Houston, Texas, 77073, US
Last Update: 2025-12-09
Between 800 and 849

Baker Hughes (NASDAQ: BKR) is an energy technology company that provides solutions for energy and industrial customers worldwide. Built on a century of experience and conducting business in over 120 countries, our innovative technologies and services are taking energy forward – making it safer, cleaner and more efficient for people and the planet. For more than a century, our inventions have revolutionized energy. We harness the power of engineering, data, and science to redefine what's possible. Our diverse portfolio of equipment and service capabilities span the energy and industrial value chain. Our two operating segments, Oilfield Services & Equipment (OFSE) and Industrial & Energy Technology (IET), are organized based on the nature of our markets and customers, and consist of similar products and services. Visit us at bakerhughes.com to learn more.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 65,278
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/weatherford.jpeg
Weatherford
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/bhge.jpeg
Baker Hughes
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Weatherford
100%
Compliance Rate
0/4 Standards Verified
Baker Hughes
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Weatherford in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Baker Hughes in 2025.

Incident History — Weatherford (X = Date, Y = Severity)

Weatherford cyber incidents detection timeline including parent company and subsidiaries

Incident History — Baker Hughes (X = Date, Y = Severity)

Baker Hughes cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/weatherford.jpeg
Weatherford
Incidents

No Incident

https://images.rankiteo.com/companyimages/bhge.jpeg
Baker Hughes
Incidents

No Incident

FAQ

Baker Hughes company demonstrates a stronger AI Cybersecurity Score compared to Weatherford company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Baker Hughes company has disclosed a higher number of cyber incidents compared to Weatherford company.

In the current year, Baker Hughes company and Weatherford company have not reported any cyber incidents.

Neither Baker Hughes company nor Weatherford company has reported experiencing a ransomware attack publicly.

Neither Baker Hughes company nor Weatherford company has reported experiencing a data breach publicly.

Neither Baker Hughes company nor Weatherford company has reported experiencing targeted cyberattacks publicly.

Neither Weatherford company nor Baker Hughes company has reported experiencing or disclosing vulnerabilities publicly.

Neither Weatherford nor Baker Hughes holds any compliance certifications.

Neither company holds any compliance certifications.

Baker Hughes company has more subsidiaries worldwide compared to Weatherford company.

Baker Hughes company employs more people globally than Weatherford company, reflecting its scale as a Oil and Gas.

Neither Weatherford nor Baker Hughes holds SOC 2 Type 1 certification.

Neither Weatherford nor Baker Hughes holds SOC 2 Type 2 certification.

Neither Weatherford nor Baker Hughes holds ISO 27001 certification.

Neither Weatherford nor Baker Hughes holds PCI DSS certification.

Neither Weatherford nor Baker Hughes holds HIPAA certification.

Neither Weatherford nor Baker Hughes holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N