Comparison Overview
オーストラリア大使館 Australian Embassy, Japan

オーストラリア大使館 Australian Embassy, Japan
2-1-14 Mita, Minato-ku, Tokyo, JP, 108-8361
Last Update: 02/04/2026
在日オーストラリア大使館は、オーストラリア政府の代表として、日本におけるオーストラリアの国益を促進します。オーストラリアの前向きなイメージを広め、日本在住のオーストラリア人に対し、領事関連情報やサービスを提供しています。 The Australian Embassy, Tokyo, represents the Australian Government and promotes Australia's interests in Japan. It works to project a positive image of Austr...

National Institute of Statistics and Geography of Mexico (INEGI)
Av. Héroe de Nacozari Sur 2301, Aguascalientes, 20276, MX
Last Update: 02/04/2026
The National Institute of Statistics and Geography of Mexico (INEGI) is an autonomous institution of the Federal Public Sector. INEGI is the coordinator of the National System of Statistical and Geographical Information of Mexico. The main objective of INEGI is to pr...
Compliance Ranges Comparison

オーストラリア大使館 Australian Embassy, Japan







National Institute of Statistics and Geography of Mexico (INEGI)






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for オーストラリア大使館 Australian Embassy, Japan in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for National Institute of Statistics and Geography of Mexico (INEGI) in 2026.
Incident History - オーストラリア大使館 Australian Embassy, Japan (X = Date, Y = Severity)
オーストラリア大使館 Australian Embassy, Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Institute of Statistics and Geography of Mexico (INEGI) (X = Date, Y = Severity)
National Institute of Statistics and Geography of Mexico (INEGI) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

オーストラリア大使館 Australian Embassy, Japan

National Institute of Statistics and Geography of Mexico (INEGI)
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.