Comparison Overview

Volvo Cars

VS

Stellantis

Volvo Cars

Assar Gabrielssons väg, Göteborg, SE
Last Update: 2025-12-10
Between 750 and 799

Everything we do starts with people. Our purpose is to provide freedom to move, in a personal, sustainable and safe way. We are committed to simplifying our customers’ lives by offering better technology solutions that improve their impact on the world and bringing the most advanced mobility innovations to protect them, their loved ones and the people around them. Volvo Cars’ continued success is the result of a collaborative, diverse, and inclusive working environment. The people of Volvo Cars are committed to making a difference in our world. Today, we are one of the most well-known and respected car brands, with over 40,000 employees across the globe. We believe in bringing out the best in each other and harnessing the true power of people. At Volvo Cars your career is designed around your talents and aspirations so you can reach your full potential. Join us on a journey of a lifetime as we create safety, autonomous driving and electrification technologies of tomorrow. Read about our privacy policy here: http://volvoca.rs/privacy

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 23,024
Subsidiaries: 4
12-month incidents
0
Known data breaches
1
Attack type number
1

Stellantis

Amsterdam, NL
Last Update: 2025-12-11
Between 600 and 649

Our storied and iconic brands embody the passion of their visionary founders and today’s customers in their innovative products and services: they include Abarth, Alfa Romeo, Chrysler, Citroën, Dodge, DS Automobiles, Fiat, Jeep®, Lancia, Maserati, Opel, Peugeot, Ram, Vauxhall and mobility brands Free2move and Leasys. Powered by our diversity, we lead the way the world moves – aspiring to become the greatest sustainable mobility tech company, not the biggest, while creating added value for all stakeholders as well as the communities in which we operate.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 96,409
Subsidiaries: 30
12-month incidents
3
Known data breaches
3
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/volvocars.jpeg
Volvo Cars
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/stellantis.jpeg
Stellantis
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
Volvo Cars
100%
Compliance Rate
0/4 Standards Verified
Stellantis
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Volvo Cars in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

Stellantis has 400.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Volvo Cars (X = Date, Y = Severity)

Volvo Cars cyber incidents detection timeline including parent company and subsidiaries

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

Stellantis cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/volvocars.jpeg
Volvo Cars
Incidents

Date Detected: 6/2021
Type:Breach
Attack Vector: Database access, CICD access, Atlassian access, Domain access, WiFi hotspots and logins, Auth bearers, API access, PAC security access
Motivation: Monetary gain through data sale
Blog: Blog
https://images.rankiteo.com/companyimages/stellantis.jpeg
Stellantis
Incidents

Date Detected: 10/2025
Type:Breach
Attack Vector: OAuth Token Exploitation, Third-Party Integration (Salesloft's Drift AI chat tool), Salesforce Environment Pivoting
Motivation: Data Theft for Extortion, Phishing Campaign Enablement, Dark Web Data Monetization
Blog: Blog

Date Detected: 9/2025
Type:Breach
Attack Vector: Compromised Third-Party Service Provider, Stolen OAuth Tokens, Salesforce Integration Exploitation
Motivation: Data Theft, Extortion, Phishing Enablement
Blog: Blog

Date Detected: 5/2025
Type:Breach
Motivation: Likely financial gain (data exploitation for scams/phishing)
Blog: Blog

FAQ

Volvo Cars company demonstrates a stronger AI Cybersecurity Score compared to Stellantis company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Stellantis company has faced a higher number of disclosed cyber incidents historically compared to Volvo Cars company.

In the current year, Stellantis company has reported more cyber incidents than Volvo Cars company.

Neither Stellantis company nor Volvo Cars company has reported experiencing a ransomware attack publicly.

Both Stellantis company and Volvo Cars company have disclosed experiencing at least one data breach.

Neither Stellantis company nor Volvo Cars company has reported experiencing targeted cyberattacks publicly.

Neither Volvo Cars company nor Stellantis company has reported experiencing or disclosing vulnerabilities publicly.

Neither Volvo Cars nor Stellantis holds any compliance certifications.

Neither company holds any compliance certifications.

Stellantis company has more subsidiaries worldwide compared to Volvo Cars company.

Stellantis company employs more people globally than Volvo Cars company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Volvo Cars nor Stellantis holds SOC 2 Type 1 certification.

Neither Volvo Cars nor Stellantis holds SOC 2 Type 2 certification.

Neither Volvo Cars nor Stellantis holds ISO 27001 certification.

Neither Volvo Cars nor Stellantis holds PCI DSS certification.

Neither Volvo Cars nor Stellantis holds HIPAA certification.

Neither Volvo Cars nor Stellantis 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