Comparison Overview

Christian Dior Couture

VS

Louis Vuitton

Christian Dior Couture

30 avenue Montaigne, Paris, Île de France, FR, 75008
Last Update: 2025-12-19

Welcome to Christian Dior Couture, House of Dreams, House of Talents. Christian Dior was the designer of dreams. In founding his House in 1947, marked by the revolution of the New Look, he metamorphosed his reveries into wonderful creations. His visionary spirit never ceased to make Clients all over the world feel more beautiful, an inspiration for his successors to this day. Christian Dior Couture, the House of Dreams, is recognized for its French heritage & vibrant culture sublimating its unique Savoir-faire and Creativity through empowering "metiers d’art”. Our Maison is a destination for sustainable growth & success where we shape the future of our Talents in a positive, authentic & generous environment. We bloom & deliver excellence with passion, determination, courage & optimism to offer meaningful & daring codes. Rich in exceptional heritage, with a community of more than 12000 talents, our House embodies Christian Dior’s “House of Talents” today more than ever.

NAICS: 4483
NAICS Definition: Jewelry, Luggage, and Leather Goods Stores
Employees: 13,418
Subsidiaries: 0
12-month incidents
3
Known data breaches
3
Attack type number
2

Louis Vuitton

2 Rue du Pont Neuf, None, Paris, None, FR, 75001
Last Update: 2025-12-19
Between 750 and 799

For more than 150 years, men and women at Louis Vuitton have shared the same spirit of excellence and passion, reaffirming their expertise every day, the world over. With us, every career is a journey, filled with excitement and challenge, desire and daring. There is no better way to reveal your potential. Explore, develop, innovate, create... Every journey is unique. Today, Louis Vuitton invites you to discover your own.

NAICS: 4483
NAICS Definition: Jewelry, Luggage, and Leather Goods Stores
Employees: 25,945
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/christian-dior-couture.jpeg
Christian Dior Couture
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/louis-vuitton.jpeg
Louis Vuitton
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
Christian Dior Couture
100%
Compliance Rate
0/4 Standards Verified
Louis Vuitton
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Luxury Goods and Jewelry Industry Average (This Year)

Christian Dior Couture has 275.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Retail Luxury Goods and Jewelry Industry Average (This Year)

Louis Vuitton has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Christian Dior Couture (X = Date, Y = Severity)

Christian Dior Couture cyber incidents detection timeline including parent company and subsidiaries

Incident History — Louis Vuitton (X = Date, Y = Severity)

Louis Vuitton cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/christian-dior-couture.jpeg
Christian Dior Couture
Incidents

Date Detected: 9/2025
Type:Breach
Blog: Blog

Date Detected: 5/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 1/2025
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/louis-vuitton.jpeg
Louis Vuitton
Incidents

Date Detected: 7/2025
Type:Breach
Motivation: Financial Gain, Fraud Enablement, Identity Theft, Data Monetization (Dark Web Sales)
Blog: Blog

FAQ

Louis Vuitton company demonstrates a stronger AI Cybersecurity Score compared to Christian Dior Couture company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Christian Dior Couture company has faced a higher number of disclosed cyber incidents historically compared to Louis Vuitton company.

In the current year, Christian Dior Couture company has reported more cyber incidents than Louis Vuitton company.

Neither Louis Vuitton company nor Christian Dior Couture company has reported experiencing a ransomware attack publicly.

Both Louis Vuitton company and Christian Dior Couture company have disclosed experiencing at least one data breach.

Christian Dior Couture company has reported targeted cyberattacks, while Louis Vuitton company has not reported such incidents publicly.

Neither Christian Dior Couture company nor Louis Vuitton company has reported experiencing or disclosing vulnerabilities publicly.

Neither Christian Dior Couture nor Louis Vuitton holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Christian Dior Couture company nor Louis Vuitton company has publicly disclosed detailed information about the number of their subsidiaries.

Louis Vuitton company employs more people globally than Christian Dior Couture company, reflecting its scale as a Retail Luxury Goods and Jewelry.

Neither Christian Dior Couture nor Louis Vuitton holds SOC 2 Type 1 certification.

Neither Christian Dior Couture nor Louis Vuitton holds SOC 2 Type 2 certification.

Neither Christian Dior Couture nor Louis Vuitton holds ISO 27001 certification.

Neither Christian Dior Couture nor Louis Vuitton holds PCI DSS certification.

Neither Christian Dior Couture nor Louis Vuitton holds HIPAA certification.

Neither Christian Dior Couture nor Louis Vuitton holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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