Comparison Overview
Frana Companies
Frana Companies
633 2nd Avenue South, Hopkins, 55343, US
Last Update: 30/03/2026
Building for the long haul since 1977. • We are a recognized leader in building multi-family housing. • We are the best wood-framing contractor in the business. • We are completely committed to quality and value. • We practice innovative craftsmanship to provide ...
Skanska
Warfvinges väg 25 (Group Headquarters), Stockholm, SE, SE-112 74
Last Update: 01/04/2026
Skanska Group uses knowledge & foresight to shape the way people live, work, and connect. More than 138 years in the making, we’re one of the world’s largest development and construction companies, with 2024 revenue totaling SEK 177 billion. We operate in select markets...
Compliance Ranges Comparison
Frana Companies
Skanska
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Frana Companies in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Skanska in 2026.
Incident History - Frana Companies (X = Date, Y = Severity)
Frana Companies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Skanska (X = Date, Y = Severity)
Skanska cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Frana Companies
Skanska
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: *.*.