Comparison Overview
Prairies Economic Development Canada I Développement économique Canada pour les Prairies

Prairies Economic Development Canada I Développement économique Canada pour les Prairies
9700 Jasper Ave NW, Edmonton, T5J 4H7, CA
Last Update: 10/03/2026
Prairies Economic Development Canada (PrairiesCan) is the department that diversifies the economy across the Canadian Prairies. PrairiesCan leads in building a strong, competitive Canadian economy by supporting business, innovation and community economic development uni...

National Park Service
1849 C Street N.W., Washington, D.C., US, 20240
Last Update: 02/04/2026
Most people know that the National Park Service cares for national parks, a network of over 420 natural, cultural and recreational sites across the nation. The treasures in this system – the first of its kind in the world – have been set aside by the American people to ...
Compliance Ranges Comparison

Prairies Economic Development Canada I Développement économique Canada pour les Prairies







National Park Service






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Prairies Economic Development Canada I Développement économique Canada pour les Prairies in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for National Park Service in 2026.
Incident History - Prairies Economic Development Canada I Développement économique Canada pour les Prairies (X = Date, Y = Severity)
Prairies Economic Development Canada I Développement économique Canada pour les Prairies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Park Service (X = Date, Y = Severity)
National Park Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prairies Economic Development Canada I Développement économique Canada pour les Prairies

National Park Service
FAQ
Latest Global CVEs
A security flaw has been discovered in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. This affects the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape results in improper neutralization of directives in dynamically evaluated code. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypass per-IP rate limits on login, one-time passcode, and password validation endpoints, enabling brute-force attacks, and to falsify IP addresses recorded in audit logs.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate valid accounts and reveal the authentication provider of SSO-only users.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a stored HTML injection vulnerability because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping. Attackers with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users.
Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.