Comparison Overview
eBerry by Strawberry
eBerry by Strawberry
Evenemangsgatan 48, Solna, SE
Last Update: 20/03/2026
During 2016 we established eBerry within Strawberry (formerly Nordic Choice Hotels). Our main mission is to transform the digital landscape for how our guests book, travel and interact with us. Our ambition is high, we want to create the world's best digital guest journ...
YouTube
901 Cherry Ave., San Bruno, 94066, US
Last Update: 23/06/2026
YouTube is a team-oriented, creative workplace where every single employee has a voice in the choices we make and the features we implement. We work together in small teams to design, develop, and roll out key features and products in very short time frames. Which means...
Compliance Ranges Comparison
eBerry by Strawberry
YouTube
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for eBerry by Strawberry in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
YouTube has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - eBerry by Strawberry (X = Date, Y = Severity)
eBerry by Strawberry cyber incidents detection timeline including parent company and subsidiaries.
Incident History - YouTube (X = Date, Y = Severity)
YouTube cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
eBerry by Strawberry
YouTube
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: *.*.