Comparison Overview
Groupe Pierre & Vacances - Center Parcs

Groupe Pierre & Vacances - Center Parcs
11 rue de Cambrai, Paris, 75019, FR
Last Update: 15/05/2026
Leader européen du tourisme de proximité, le Groupe Pierre & Vacances-Center Parcs développe et gère – depuis plus de 50 ans – des concepts de vacances et de loisirs innovants dans le respect de l’environnement. Son business model repose sur deux métiers complémentaires...

Royal Caribbean Group
Royal Caribbean Group 1050 Caribbean Way Miami, Miami, Florida, US, 2312
Last Update: 01/04/2026
At Royal Caribbean Group, we deliver unforgettable vacations to guests who trust us with life’s greatest moments. We build the best ships, and even better careers, all while doing the right thing. We are passionate. We are innovative. We are unstoppable. We open the wor...
Compliance Ranges Comparison

Groupe Pierre & Vacances - Center Parcs







Royal Caribbean Group






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
Groupe Pierre & Vacances - Center Parcs has 60.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Royal Caribbean Group in 2026.
Incident History - Groupe Pierre & Vacances - Center Parcs (X = Date, Y = Severity)
Groupe Pierre & Vacances - Center Parcs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Royal Caribbean Group (X = Date, Y = Severity)
Royal Caribbean Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Groupe Pierre & Vacances - Center Parcs

Royal Caribbean Group
FAQ
Latest Global CVEs
A security flaw has been discovered in SourceCodester Onlne Examination & Learning Management System 1.0. Affected by this vulnerability is the function pathinfo of the file /upload_files.php of the component Filename Extension. Performing a manipulation results in unrestricted upload. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The name of the affected product appears to have a typo in it.
A vulnerability was identified in SourceCodester Onlne Examination & Learning Management System 1.0. Affected is an unknown function of the file /process_lesson.php. Such manipulation of the argument user_id leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly available and might be used. The name of the affected product appears to have a typo in it.
A vulnerability was determined in itsourcecode Hospital Management System 1.0. This impacts an unknown function of the file /paymentdischarge.php. This manipulation of the argument patientid causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
A vulnerability was found in itsourcecode Hospital Management System 1.0. This affects an unknown function of the file /payment.php. The manipulation of the argument patientid results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used.
Zephyr's DNS resolver detects mDNS (.local) queries in dns_resolve_name_internal() (subsys/net/lib/dns/resolve.c) with memcmp(strrchr(query, '.'), ".local", 7), which always reads a fixed 7 bytes from the suffix pointer. When the resolved hostname's final label is shorter than 7 bytes (e.g. names ending in .org, .com, .net, .io, or a trailing dot), the comparison reads 1-2 bytes past the string's NUL terminator. The hostname (query) is the caller-supplied name passed through the standard getaddrinfo()/dns_get_addr_info()/dns_resolve_name() path and is influenceable by operators or remote inputs (server names from configuration, parsed URLs, or app-facing interfaces). On a tightly-sized buffer with no slack (for example a userspace getaddrinfo call where the hostname is copied with k_usermode_string_alloc_copy to exactly strlen+1 bytes), the over-read crosses the allocation boundary; if that boundary is unmapped (guard page, memory-domain boundary under MPU, or an address sanitizer) the over-read faults, causing a denial of service. The over-read bytes are never returned, so there is no information disclosure. The flaw is compiled only when CONFIG_MDNS_RESOLVER is enabled, exists since v1.10.0, and is fixed by replacing the fixed-length memcmp with a NUL-safe strcmp(ptr, ".local").