Comparison Overview
ORIX Corporation USA

ORIX Corporation USA
280 Park Avenue 40 West, None, New York, NY, US, 10017
Last Update: 03/04/2026
Established in the U.S. in 1981, ORIX USA has grown organically and through acquisition into the investment and asset management firm we are today. With a specialization in private credit, real estate, and private equity solutions for middle-market focused borrowers and...

Chase
270 Park Avenue, New York, 10172, US
Last Update: 14/09/2026
At Chase, we’re dedicated to helping you succeed. Whether you’re in need of banking, credit cards, mortgages, auto financing, investment guidance, small business support, or payment solutions, we’re beside you every step of the way. For customer service, contact us via...
Compliance Ranges Comparison

ORIX Corporation USA







Chase






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

ORIX Corporation USA

Chase
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)