Comparison Overview
Jennings O'Donovan & Partners
Jennings O'Donovan & Partners
Finisklin Business Park, Sligo, Connacht, IE, F91 RHH9
Last Update: 01/04/2026
Jennings O’Donovan is a multidisciplinary consulting engineering firm specialising in renewable energy, water supply, wastewater treatment and in the provision of planning and environmental services. Founded in 1950, the company, has offices across the country in Sligo...
Fugro
Veurse Achterweg 10, Leidschendam, 2264 SG, NL
Last Update: 01/04/2026
We are the world’s leading Geo-data specialist, collecting and analysing comprehensive information about the Earth and the structures built upon it. Through integrated data acquisition, analysis and advice, we unlock insights from Geo-data to help our clients design, bu...
Compliance Ranges Comparison
Jennings O'Donovan & Partners
Fugro
Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Jennings O'Donovan & Partners in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Fugro in 2026.
Incident History - Jennings O'Donovan & Partners (X = Date, Y = Severity)
Jennings O'Donovan & Partners cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fugro (X = Date, Y = Severity)
Fugro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Jennings O'Donovan & Partners
Fugro
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: *.*.