Tiffany & Co. has confirmed a data breach affecting customers in South Korea, marking the second such incident involving an LVMH Moët Hennessy Louis Vuitton brand after a similar case at Dior. On May 26, Tiffany Korea notified select customers via email of a cybersecurity breach involving unauthorized access to a vendor platform used for managing customer data.
Both Dior and Tiffany operate under LVMH, the world’s largest luxury goods conglomerate, raising broader concerns over data security within the group.
According to the email sent by Tiffany Korea, the breach occurred on Apr. 8. The company said it verified on May 9 that personal data belonging to individuals in South Korea had been compromised. The exposed information includes names, addresses, phone numbers, email addresses, internal customer ID numbers, and purchase history—data considered particularly sensitive from a consumer standpoint, as was the case in the Dior breach.
Tiffany noted that, as of now, there have been no confirmed cases of misuse or exploitation of the compromised data.
When contacted by Chosunilbo, Tiffany Korea’s customer service center said that only those affected had been individually notified. No public notice regarding the breach appeared on the company’s official website at the time of reporting.
LVMH finalized its acquisition of Tiffany & Co., the American luxury jeweler, in January 2021 in a deal valued at approximately 17 trillion won ($12.4 billion). Tiffany Korea generated 377.9 billion won ($276 million) in domestic sales last year, a 7.6% increase from the previous year, with operating profit reaching 21.5 billion won ($15.7 million)
A critical vulnerability in ModSecurity’s Apache module has been disclosed, potentially exposing millions of web servers worldwide to denial-of-service attacks.
The flaw, tracked as CVE-2025-47947 and assigned a CVSS score of 7.5, affects the popular open-source web application firewall’s handling of JSON payloads under specific conditions.
Security researchers have confirmed that attackers can exploit this vulnerability with minimal effort, requiring only a single crafted request to consume excessive server memory and potentially crash targeted systems.
ModSecurity DoS Flaw (CVE-2025-47947)
The vulnerability was initially reported in March 2025 by Simon Studer from Netnea on behalf of Swiss Post, though it took several months for developers to successfully reproduce and understand the root cause.
CVE-2025-47947 specifically affects mod_security2, the Apache module version of ModSecurity, while the newer libmodsecurity3 implementation remains unaffected.
The flaw emerges when two specific conditions are met simultaneously: the incoming payload must have a Content-Type of application/json, and there must be at least one active rule utilizing the sanitiseMatchedBytes action.
