Comparison Overview
Régie de l’énergie du Canada
Régie de l’énergie du Canada
N/A
Last Update: 28/11/2025
Nous sommes la Régie de l’énergie du Canada. Nous travaillons pour vous afin d’assurer le déplacement sûr de l’énergie partout au Canada. Nous travaillons dans l’intérêt du public. Cela signifie que nous rendons des décisions en fonction de ce qui importe à tous plutôt ...
Swiss Federal Administration
Eigerstrasse 71, Bern, 3003, CH
Last Update: 06/08/2026
Seven departments, the Federal Chancellery and around 70 administrative units make up the Federal Administration. With around 38,000 employees, we are one of the largest employers in Switzerland. Everyone who works for the Federal Administration actively contributes t...
Compliance Ranges Comparison
Régie de l’énergie du Canada
Swiss Federal Administration
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Régie de l’énergie du Canada in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Swiss Federal Administration has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Régie de l’énergie du Canada (X = Date, Y = Severity)
Régie de l’énergie du Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swiss Federal Administration (X = Date, Y = Severity)
Swiss Federal Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Régie de l’énergie du Canada
Swiss Federal Administration
FAQ
Latest Global CVEs
A vulnerability was found in ggml-org llama.cpp bec4772f6. The impacted element is the function deserialize_tensor of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Performing a manipulation of the argument op/op_params results in deserialization. The attack may be initiated remotely. This vulnerability is distinct from CVE-2026-34159 (GHSA-j8rj-fmpv-wcxw, PR #20908), which only added a buffer==nullptr rejection in create_node() and does not validate op or op_params. The reported GitHub issue was closed automatically due to inactivity.
A vulnerability has been found in CTFd up to 3.8.4. The affected element is the function _is_safe_url of the file CTFd/utils/validators/__init__.py. Such manipulation of the argument Next leads to open redirect. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9. Upgrading the affected component is recommended.
- https://github.com/CTFd/CTFd/
- https://github.com/CTFd/CTFd/commit/5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9
- https://github.com/CTFd/CTFd/pull/3026
- https://github.com/CTFd/CTFd/releases/tag/3.8.4
- https://mblunt.dev/writeups/ctfd-open-redirect/
- https://vuldb.com/cve/CVE-2026-78145
- https://vuldb.com/submit/882469
- https://vuldb.com/vuln/394533
- https://vuldb.com/vuln/394533/cti
A vulnerability was identified in code-projects Barangay Resident Profiling Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /boarders.php of the component Boarder Management Module. Such manipulation of the argument ID leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used.
A vulnerability was determined in code-projects Barangay Resident Profiling Management System 1.0. Affected is an unknown function of the file residents.php of the component Resident Search Functionality. This manipulation of the argument Search causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
A vulnerability was found in code-projects Barangay Resident Profiling Management System 1.0. This impacts an unknown function of the file /archived_records.php of the component Restore/Delete. The manipulation of the argument resident_id results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used.