Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

RIMOWARIMOWA
VS
KeringKering
RIMOWA

RIMOWA

Richard-Byrd-Str. 13, Köln, North-Rhine-Westphalia, DE, 50829

Last Update: 15/03/2026

View Profile
Between 750 and 799
https://www.rimowa.com
774/1000Fair

Welcome to RIMOWA, the first German Maison of the LVMH Group. We are a global lifestyle brand with a mission to create the essential tools for a lifetime of travel. For more than 120 years, we’ve dedicated ourselves to develop unique products where function coexists w...

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

Kering

40, rue de Sèvres, PARIS, 75007, FR

Last Update: 01/04/2026

View Profile
Between 700 and 749
https://www.kering.com/en
738/1000Moderate

Kering is a global, family-led luxury group, home to people whose passion and expertise nurture creative Houses across ready-to-wear and couture, leather goods, jewelry, eyewear and beauty: Gucci, Saint Laurent, Bottega Veneta, Balenciaga, McQueen, Brioni, Boucheron, Po...

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

Compliance Ranges Comparison

Based On Specific Ai Models Category
RIMOWA

RIMOWA

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Kering

Kering

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

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

No incidents recorded for RIMOWA in 2026.

Incidents

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

No incidents recorded for Kering in 2026.

Incidents

Incident History - RIMOWA (X = Date, Y = Severity)

RIMOWA cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - Kering (X = Date, Y = Severity)

Kering cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
RIMOWA

RIMOWA

Incidents
No explicit notable incidents reported.
Kering

Kering

Incidents
🔒 Incident : Cyber Attack
KER0692106091525
🔒 Incident : Breach
KER3565635100325

FAQ

Between RIMOWA company and Kering company, which one has the best AI Cybersecurity Score ?
Between RIMOWA company and Kering company, which one has experienced more cyber incidents in the past ?
Between RIMOWA company and Kering company, which one has experienced more cyber incidents this year ?
Between RIMOWA company and Kering company, which one has experienced at least one ransomware attack ?
Between RIMOWA company and Kering company, which one has experienced at least one data breach ?
Between RIMOWA company and Kering company, which one has experienced at least one targeted cyberattack ?
Between RIMOWA company and Kering company, which one has experienced at least one vulnerability ?
Between RIMOWA company and Kering company, which one holds the most compliance certifications ?
Between RIMOWA company and Kering company, which one holds the fewest compliance certifications ?
Between RIMOWA company and Kering company, which one has the most subsidiaries ?
Between RIMOWA company and Kering company, which one has the largest number of employees ?
Between RIMOWA and Kering, which company holds both SOC 2 Type 1 certifications ?
Between RIMOWA and Kering, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - RIMOWA or Kering ?
Which company is PCI DSS compliant - RIMOWA or Kering ?
Between RIMOWA and Kering, which company complies with HIPAA regulations for healthcare data ?
Between RIMOWA and Kering, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-12175
SUMMARY

A vulnerability was detected in CodeAstro Student Attendance Management System 1.0. Impacted is an unknown function of the file /attendance-php/Admin/createStudents.php. Performing a manipulation of the argument admissionNumber results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used.

PUBLISHED
Date2026-06-13
UPDATED
Date2026-06-13
RISK INFORMATION (Score: 4.7)
CVSS2
Base Score: 5.8
Complexity: LOW
AV:N/AC:L/Au:M/C:P/I:P/A:P
CVSS3
Base Score: 4.7
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 2.0
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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
IMPACT SCORE
3.4
EXPLOITABILITY
1.2
CVE-2026-12174
SUMMARY

A security vulnerability has been detected in D-Link DCS-935L 1.10.01. This issue affects the function snprintf of the file /web/cgi-bin/greece/rhea of the component HTTP Handler. Such manipulation of the argument data leads to format string. The attack may be launched remotely. The exploit has been disclosed publicly and may be used.

PUBLISHED
Date2026-06-13
UPDATED
Date2026-06-13
RISK INFORMATION (Score: 8.8)
CVSS2
Base Score: 9.0
Complexity: LOW
AV:N/AC:L/Au:S/C:C/I:C/A:C
CVSS3
Base Score: 8.8
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS4
Base Score: 7.4
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
IMPACT SCORE
5.9
EXPLOITABILITY
2.8
CVE-2026-12183
SUMMARY

Nefteprodukttekhnika BUK TS-G Gas Station Automation System 2.9.1 through 2.10.2 on Linux contains an Improper Authentication vulnerability (CWE-287) in the system configuration module. The /php/ajax-login.php endpoint returns userid=1 (administrator) in response to any HTTP POST request that supplies arbitrary credentials (e.g., action=dologin&login=<any_value>&pwd=<any_value>), and subsequent privileged endpoints under /php/ajax-main.php and /modules/* do not validate a server-side session. A remote unauthenticated attacker can invoke any administrative action exposed by the configuration module, including reading and modifying user rules, fuel tank gauges, fuel dispensers, relays, cash registers, bank terminals, fuel cards, price and customer displays, cash collection, and pricing rules.

PUBLISHED
Date2026-06-13
UPDATED
Date2026-06-13
RISK INFORMATION (Score: 9.8)
CVSS3
Base Score: 9.8
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS4
Base Score: 9.3
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/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
IMPACT SCORE
5.9
EXPLOITABILITY
3.9
CVE-2026-6428
SUMMARY

SQL Injection in reports/catalogue_out.pl in Koha Community Koha through 22.11.37, 23.x, 24.x before 24.11.16, 25.05.x before 25.05.11, 25.11.x before 25.11.05, 26.05.x before 26.05.01, and 26.11.x before 26.11.00 allows an authenticated staff user with the Reports module flag to read arbitrary data from the Koha application database via the Filter URL parameter when the Criteria parameter matches /branchcode/. The vulnerable sink in sub calculate concatenates the unmodified Filter request parameter directly into a LIKE clause of the auxiliary $strsth2 statement and executes it via DBI without bound parameters: my $f = @$filters[0]; $f =~ s/\*/%/g; $strsth2 .= " AND $column LIKE '$f' "; This enables error-based SQL injection (e.g., via EXTRACTVALUE) and full read access to sensitive tables including borrowers (password hashes, 2FA secrets, PII), borrower_password_recovery, api_keys, and sessions. Proof of concept (error-based, single request): GET /cgi-bin/koha/reports/catalogue_out.pl?do_it=1&output=screen&Limit=10&Criteria=branchcode&Filter=x'+AND+EXTRACTVALUE(1,CONCAT(0x7e,VERSION(),0x7c,USER(),0x7c,DATABASE(),0x7e))--+- Cookie: CGISESSID=<LIBRARIAN_SESSION> The response body contains the DBI exception leaking the MariaDB version, database user, client IP, and database name, after which arbitrary data can be paged out using LIMIT n,1 / SUBSTRING(...). The vulnerable sink was introduced in commit 6bb77ae3e4 (2008-07-09); CVE-2015-4633 patched the same class in sibling files but did not generalise the fix to reports/catalogue_out.pl. Fixed in Koha 22.11.38, 24.11.16, 25.05.11, 25.11.05, 26.05.01, and 26.11.00 by replacing the raw concatenation with a parameterised placeholder.

PUBLISHED
Date2026-06-13
UPDATED
Date2026-06-13
RISK INFORMATION (Score: 7.6)
CVSS2
Base Score: 7.5
Complexity: LOW
AV:N/AC:L/Au:S/C:C/I:N/A:P
CVSS3
Base Score: 7.6
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
CVSS4
Base Score: 5.6
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/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:Y/R:X/V:C/RE:X/U:Amber
IMPACT SCORE
4.7
EXPLOITABILITY
2.8
CVE-2026-5513
SUMMARY

The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bookly-customer-full-name' cookie in versions up to, and including, 27.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires 'Remember personal information in cookies' setting to be enabled (disabled by default).

PUBLISHED
Date2026-06-13
UPDATED
Date2026-06-13
RISK INFORMATION (Score: 7.2)
CVSS3
Base Score: 7.2
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
IMPACT SCORE
2.7
EXPLOITABILITY
3.9