Comparison Overview

Wyman Gordon

VS

Textron

Wyman Gordon

10825 Telge Rd, Houston, Texas, 77095, US
Last Update: 2025-05-06 (UTC)

Wyman-Gordon is the premier forging company for the global aerospace and energy markets. Providing a specialized service, Wyman-Gordon manufactures forged components from high grade titanium and nickel based alloys. Such components are used for jet engines, including fan disks, compressor disks, turbine disks, and shafts. We also produce titanium and steel forgings for airframes, including wing beams, wing boxes, door and window frames, as well as nacelle and landing gear components. Wyman-Gordon also extrudes steel products for use in power plants and oil and gas industry applications. Our reputation, market position, and operational efficiency are reliant upon our demonstrated ability to continually improve. Major Markets: Aerospace, Power Generation, Oil & Gas Exploration, Medical, Automotive, Locomotive, Food Processing, Nuclear

NAICS: 3364
NAICS Definition: Aerospace Product and Parts Manufacturing
Employees: 1,019
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Textron

40 Westminster, Providence, RI, 02903, US
Last Update: 2025-05-06 (UTC)
Between 750 and 799

Textron Inc. is a multi-industry company that leverages its global network of aircraft, defense, industrial and finance businesses to provide customers with innovative solutions and services. Textron is known around the world for its powerful brands such as Bell, Cessna, Beechcraft, Pipistrel, Jacobsen, Kautex, Lycoming, E-Z-GO, Arctic Cat, and Textron Systems. For more information, visit: www.textron.com.

NAICS: 3364
NAICS Definition: Aerospace Product and Parts Manufacturing
Employees: 25,848
Subsidiaries: 20
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/wyman-gordon.jpeg
Wyman Gordon
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/textron.jpeg
Textron
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
Wyman Gordon
100%
Compliance Rate
0/4 Standards Verified
Textron
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Aviation and Aerospace Component Manufacturing Industry Average (This Year)

No incidents recorded for Wyman Gordon in 2025.

Incidents vs Aviation and Aerospace Component Manufacturing Industry Average (This Year)

No incidents recorded for Textron in 2025.

Incident History — Wyman Gordon (X = Date, Y = Severity)

Wyman Gordon cyber incidents detection timeline including parent company and subsidiaries

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

Textron cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/wyman-gordon.jpeg
Wyman Gordon
Incidents

No Incident

https://images.rankiteo.com/companyimages/textron.jpeg
Textron
Incidents

No Incident

FAQ

Textron company demonstrates a stronger AI Cybersecurity Score compared to Wyman Gordon company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Textron company has disclosed a higher number of cyber incidents compared to Wyman Gordon company.

In the current year, Textron company and Wyman Gordon company have not reported any cyber incidents.

Neither Textron company nor Wyman Gordon company has reported experiencing a ransomware attack publicly.

Neither Textron company nor Wyman Gordon company has reported experiencing a data breach publicly.

Neither Textron company nor Wyman Gordon company has reported experiencing targeted cyberattacks publicly.

Neither Wyman Gordon company nor Textron company has reported experiencing or disclosing vulnerabilities publicly.

Neither Wyman Gordon nor Textron holds any compliance certifications.

Neither company holds any compliance certifications.

Textron company has more subsidiaries worldwide compared to Wyman Gordon company.

Textron company employs more people globally than Wyman Gordon company, reflecting its scale as a Aviation and Aerospace Component Manufacturing.

Neither Wyman Gordon nor Textron holds SOC 2 Type 1 certification.

Neither Wyman Gordon nor Textron holds SOC 2 Type 2 certification.

Neither Wyman Gordon nor Textron holds ISO 27001 certification.

Neither Wyman Gordon nor Textron holds PCI DSS certification.

Neither Wyman Gordon nor Textron holds HIPAA certification.

Neither Wyman Gordon nor Textron holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Sakai is a Collaboration and Learning Environment. Prior to versions 23.5 and 25.0, EncryptionUtilityServiceImpl initialized an AES256TextEncryptor password (serverSecretKey) using RandomStringUtils with the default java.util.Random. java.util.Random is a non‑cryptographic PRNG and can be predicted from limited state/seed information (e.g., start time window), substantially reducing the effective search space of the generated key. An attacker who can obtain ciphertexts (e.g., exported or at‑rest strings protected by this service) and approximate the PRNG seed can feasibly reconstruct the serverSecretKey and decrypt affected data. SAK-49866 is patched in Sakai 23.5, 25.0, and trunk.

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

pypdf is a free and open-source pure-python PDF library. Prior to version 6.1.3, an attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing the content stream of a page using the LZWDecode filter. This has been fixed in pypdf version 6.1.3.

Risk Information
cvss4
Base: 6.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/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

pypdf is a free and open-source pure-python PDF library. Prior to version 6.1.3, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires parsing the content stream of a page which has an inline image using the DCTDecode filter. This has been fixed in pypdf version 6.1.3.

Risk Information
cvss4
Base: 6.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/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

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.5, Authlib’s JWE zip=DEF path performs unbounded DEFLATE decompression. A very small ciphertext can expand into tens or hundreds of megabytes on decrypt, allowing an attacker who can supply decryptable tokens to exhaust memory and CPU and cause denial of service. This issue has been patched in version 1.6.5. Workarounds for this issue involve rejecting or stripping zip=DEF for inbound JWEs at the application boundary, forking and add a bounded decompression guard via decompressobj().decompress(data, MAX_SIZE)) and returning an error when output exceeds a safe limit, or enforcing strict maximum token sizes and fail fast on oversized inputs; combine with rate limiting.

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

OpenBao is an open source identity-based secrets management system. Prior to version 2.4.2, OpenBao's audit log did not appropriately redact fields when relevant subsystems sent []byte response parameters rather than strings. This includes, but is not limited to sys/raw with use of encoding=base64, all data would be emitted unredacted to the audit log, and Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log. This issue has been patched in OpenBao 2.4.2.

Risk Information
cvss4
Base: 5.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/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