Comparison Overview

Rheinmetall

VS

Lockheed Martin

Rheinmetall

Rheinmetall Platz 1, Düsseldorf, Nordrhein Westfalen, DE, 40476
Last Update: 2025-12-17

As an integrated technology group, the listed company Rheinmetall AG, headquartered in Düsseldorf, stands for a company that is as strong in substance as it is successful internationally, and that is active in various markets with an innovative range of products and services. Rheinmetall is a leading international systems supplier in the defence industry and at the same time a driver of forward-looking technological and industrial innovations in the civilian markets. The focus on sustainability is an integral part of Rheinmetall's strategy. The company aims to achieve CO2 neutrality by 2035. Through our work in various fields, we at Rheinmetall take on responsibility in a dramatically changing world. With our technologies, products and systems, we create the indispensable basis for peace, freedom and sustainable development: security. Find more Information about your career opportunities here: https://www.rheinmetall.com/en/rheinmetall_ag/career_1/index.php IMPRINT AND DATA PROTECTION https://www.rheinmetall.com/en/rheinmetall_ag/service/imprint/index.php

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 13,148
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
2

Lockheed Martin

6801 Rockledge Drive, Bethesda, MD, US, 20817
Last Update: 2025-12-19

The world relies on what we do. Headquartered in Bethesda, Maryland, with offices across the U.S. and around the globe, our team delivers solutions that strengthen national security, shape industries and push engineering and technology to new levels. We collaborate to win. We put our customers first. And we perform with excellence. The best careers are built at Lockheed Martin. Join us.

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 102,502
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rheinmetall.jpeg
Rheinmetall
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/lockheed-martin.jpeg
Lockheed Martin
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
Rheinmetall
100%
Compliance Rate
0/4 Standards Verified
Lockheed Martin
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for Rheinmetall in 2025.

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for Lockheed Martin in 2025.

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

Rheinmetall cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lockheed Martin (X = Date, Y = Severity)

Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rheinmetall.jpeg
Rheinmetall
Incidents

Date Detected: 04/2023
Type:Ransomware
Blog: Blog

Date Detected: 03/2023
Type:Cyber Attack
Motivation: Political
Blog: Blog
https://images.rankiteo.com/companyimages/lockheed-martin.jpeg
Lockheed Martin
Incidents

Date Detected: 8/2022
Type:Cyber Attack
Attack Vector: DDoS
Motivation: Hacktivism, Disruption
Blog: Blog

FAQ

Lockheed Martin company demonstrates a stronger AI Cybersecurity Score compared to Rheinmetall company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Rheinmetall company has faced a higher number of disclosed cyber incidents historically compared to Lockheed Martin company.

In the current year, Lockheed Martin company and Rheinmetall company have not reported any cyber incidents.

Rheinmetall company has confirmed experiencing a ransomware attack, while Lockheed Martin company has not reported such incidents publicly.

Neither Lockheed Martin company nor Rheinmetall company has reported experiencing a data breach publicly.

Both Lockheed Martin company and Rheinmetall company have reported experiencing targeted cyberattacks.

Neither Rheinmetall company nor Lockheed Martin company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rheinmetall nor Lockheed Martin holds any compliance certifications.

Neither company holds any compliance certifications.

Both Lockheed Martin company and Rheinmetall company have a similar number of subsidiaries worldwide.

Lockheed Martin company employs more people globally than Rheinmetall company, reflecting its scale as a Defense and Space Manufacturing.

Neither Rheinmetall nor Lockheed Martin holds SOC 2 Type 1 certification.

Neither Rheinmetall nor Lockheed Martin holds SOC 2 Type 2 certification.

Neither Rheinmetall nor Lockheed Martin holds ISO 27001 certification.

Neither Rheinmetall nor Lockheed Martin holds PCI DSS certification.

Neither Rheinmetall nor Lockheed Martin holds HIPAA certification.

Neither Rheinmetall nor Lockheed Martin holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

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

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

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

FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by placing a crafted TextShaping.dll in the application directory. Attackers can generate a reverse shell payload using msfvenom and replace the missing DLL to achieve remote code execution when the application launches.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
Description

LDAP Tool Box Self Service Password 1.5.2 contains a password reset vulnerability that allows attackers to manipulate HTTP Host headers during token generation. Attackers can craft malicious password reset requests that generate tokens sent to a controlled server, enabling potential account takeover by intercepting and using stolen reset tokens.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/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
Description

Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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