Comparison Overview
Jindal Steel Ltd.

Jindal Steel Ltd.
Jindal Centre, 12, Bhikaiji Cama Place, Delhi, New Delhi, IN, 110066
Last Update: 20/09/2026
Jindal Steel is one of India’s foremost integrated steel producers, renowned for its scale, efficiency, and commitment to excellence. Operating on a robust mine-to-metal model, the Company leverages captive resources, advanced manufacturing capabilities, and a global di...

Maaden
Saudi Arabia, Riyadh, SA, 11537
Last Update: 07/10/2026
Maaden is Saudi Arabia’s engine of industrial transformation and one of the world’s top ten mining giants by market cap and fastest growing globally. We’re building the future of mining, creating fully integrated value chains across gold, phosphate, bauxite, copper and ...
Compliance Ranges Comparison

Jindal Steel Ltd.







Maaden






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Jindal Steel Ltd. in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Maaden in 2026.
Incident History - Jindal Steel Ltd. (X = Date, Y = Severity)
Jindal Steel Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Maaden (X = Date, Y = Severity)
Maaden cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jindal Steel Ltd.

Maaden
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.