Comparison Overview
株式会社リクリエ
株式会社リクリエ
福岡市博多駅前4-3-22, 博多駅前４−３−２２−８F, 812-0011, JP
Last Update: 17/05/2026
リクリエ自社ホテルブランド「グランドベース」を西日本エリアをメインに60施設展開しております。省人化ホテル運用事業とSaaS事業の2軸でホテルのアップデートを目指し、さらには運用だけでなく企画開発事業によって土地の利活用課題を解決することに挑戦しております。
Hilton Grand Vacations
5323 Millenia Lakes Boulevard, Orlando, 32839, US
Last Update: 03/04/2026
Hilton Grand Vacations is a global leader in vacation ownership, developing, marketing and operating a portfolio of high-quality, shared-ownership properties in highly desired vacation destinations. Our company also manages and operates innovative club membership progra...
Compliance Ranges Comparison
株式会社リクリエ
Hilton Grand Vacations
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
株式会社リクリエ has 34.21% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hilton Grand Vacations in 2026.
Incident History - 株式会社リクリエ (X = Date, Y = Severity)
株式会社リクリエ cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hilton Grand Vacations (X = Date, Y = Severity)
Hilton Grand Vacations cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
株式会社リクリエ
Hilton Grand Vacations
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.