Comparison Overview
Lument

Lument
230 Park Ave, None, New York, New York, US, 10169
Last Update: 07/03/2026
At Lument, we are redefining what you can expect from a financial partner. We have the expertise, products, resources, and, most importantly, the determination to guide you to the right financial solution for your goals. Headquartered in New York, with major offices in...

Mizuho
1–5–5 Otemachi, Chiyoda–ku, Tokyo, 100–8176, JP
Last Update: 07/09/2026
This is not your typical financial institution. It’s our people who make us a cut above. Here, every person is respected because of their differences, not in spite of them. We pride ourselves on a culture of purpose, passion and compassion. At Mizuho, we provide the st...
Compliance Ranges Comparison

Lument







Mizuho






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

Lument

Mizuho
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)