Comparison Overview
LTIMindtree Enterprise AI

LTIMindtree Enterprise AI
N/A
Last Update: 14/11/2025
At LTIMindtree, we believe in AI in Everything, Everything in AI, AI for Everyone. We focus on delivering AI and Generative AI (GenAI) offerings that help businesses achieves outcomes. We strategically partner with you to experiment, scale, reimagine, innovate and solve...

Cognizant
300 Frank W Burr Blvd, Teaneck, 07666, US
Last Update: 05/09/2026
Cognizant (Nasdaq: CTSH) is an AI Builder and technology services provider, bridging the gap between AI investment and enterprise value. We build full-stack AI solutions powered by deep industry, process and engineering expertise — embedding an organization's unique co...
Compliance Ranges Comparison

LTIMindtree Enterprise AI







Cognizant






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for LTIMindtree Enterprise AI in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Cognizant has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - LTIMindtree Enterprise AI (X = Date, Y = Severity)
LTIMindtree Enterprise AI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cognizant (X = Date, Y = Severity)
Cognizant cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

LTIMindtree Enterprise AI

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