Comparison Overview
Pyszne.pl for business
Pyszne.pl for business
ul. Rybacka 9, Warsaw, 53-656, PL
Last Update: 20/02/2026
Pyszne.pl for business is a flexible food solution that helps companies care for their employees - no matter where they work. With Pyszne.pl for business you can: • Offer a wide variety of food: With the Pyszne Pay allowance and Card your employees can enjoy delicious...
Frito-Lay
7701 Legacy Dr, Plano, 75024, US
Last Update: 04/04/2026
We believe every consumer should have access to their favorite snack, everywhere. We own the manufacturing process from seed to shelf and actively invest in technology to automate key steps of the process. This helps us be more agile in what we need to make, who we need...
Compliance Ranges Comparison
Pyszne.pl for business
Frito-Lay
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Pyszne.pl for business in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Frito-Lay in 2026.
Incident History - Pyszne.pl for business (X = Date, Y = Severity)
Pyszne.pl for business cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Frito-Lay (X = Date, Y = Severity)
Frito-Lay cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pyszne.pl for business
Frito-Lay
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: *.*.