Comparison Overview
Homer Burgess Ltd
Homer Burgess Ltd
Burgess House, Garroch Business Park, Garroch Loaning, Dumfries, Dumfriesshire DG2 8PN, GB
Last Update: 01/04/2026
Homer Burgess and its team of experienced engineers provide bespoke design solutions to clients across the UK. We specialise in the welding and fabrication of steelwork, tanks, vessels, pipework and machinery, regularly working with stainless steel, carbon steel and alu...
Bilfinger
Oskar-Meixner-Straße 1, Mannheim, 68163, DE
Last Update: 01/04/2026
Bilfinger is an international industrial services provider with a vision to be the No. 1 for its customers in enhancing efficiency and sustainability within the process industry. Bilfinger’s comprehensive portfolio spans the entire value chain, from consulting & enginee...
Compliance Ranges Comparison
Homer Burgess Ltd
Bilfinger
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Homer Burgess Ltd in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Bilfinger in 2026.
Incident History - Homer Burgess Ltd (X = Date, Y = Severity)
Homer Burgess Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bilfinger (X = Date, Y = Severity)
Bilfinger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Homer Burgess Ltd
Bilfinger
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: *.*.