Comparison Overview
Tiffany & Co.
Tiffany & Co.
727 5th Ave, New York, 10022, US
Last Update: 02/04/2026
In 1837 Charles Lewis Tiffany founded his company in New York City where his store was soon acclaimed as the palace of jewels for its exceptional gemstones. Since then TIFFANY & CO. has become synonymous with elegance, innovative design, fine craftsmanship and creative ...
Swatch Group
Seevorstadt 6, Biel, Berne, CH, 2502
Last Update: 01/04/2026
Swatch Group is the world's number one manufacturer of finished watches. With its 16 watch brands, the Group is present in all price segments, and is also active in the manufacture and sale of jewelry, watch movements and components. Swatch Group unites, among other co...
Compliance Ranges Comparison
Tiffany & Co.
Swatch Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Tiffany & Co. has 37.5% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Swatch Group in 2026.
Incident History - Tiffany & Co. (X = Date, Y = Severity)
Tiffany & Co. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swatch Group (X = Date, Y = Severity)
Swatch Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tiffany & Co.
Swatch Group
FAQ
Latest Global CVEs
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in PhialsBasement KoboldCPP-MCP-Server 1.0.0. Affected by this issue is the function makeRequest of the file src/index.ts of the component BaseConfigSchema. Executing a manipulation of the argument apiUrl can lead to server-side request forgery. It is possible to launch the attack on the local host. The project was informed of the problem early through an issue report but has not responded yet.
A security flaw has been discovered in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this vulnerability is the function fs.readFileSync of the file src/index.ts of the component upload_document. Performing a manipulation of the argument File results in path traversal. Attacking locally is a requirement. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was identified in Nikolaibibo claude-comfyui-mcp 1.0.0. Affected is the function copyFileSync of the file src/tools/utils.ts of the component comfy_upload_image. Such manipulation of the argument image_path leads to path traversal. An attack has to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.