Comparison Overview
Impact Observatory

Impact Observatory
Washington, 20008, US
Last Update: 23/06/2026
Impact Observatory is a mission-driven technology company bringing artificial intelligence (AI) powered algorithms and on-demand data to sustainability, environment, and risk analysis for governments, non-profit organizations, companies, and markets. Impact Observatory ...

Myntra
Devarabeesanahalli Main Road, Bengaluru, Karnataka, IN, 560103
Last Update: 13/09/2026
At Myntra, we don’t just follow fashion - we define it. As India's leading fashion, lifestyle, and beauty destination, we bring together the best of style, technology, and innovation to create a seamless shopping experience for our customers. With a commitment to empow...
Compliance Ranges Comparison

Impact Observatory







Myntra






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Impact Observatory has 36.71% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Myntra in 2026.
Incident History - Impact Observatory (X = Date, Y = Severity)
Impact Observatory cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Myntra (X = Date, Y = Severity)
Myntra cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Impact Observatory

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