Comparison Overview
Cortex Reply DE

Cortex Reply DE
Luise-Ullrich Straße, Munich, Bavaria, DE, 80636
Last Update: 25/04/2026
Cortex Reply is a Reply Group Company specializing in FinOps consulting. We are dedicated to helping organizations optimize their cloud financial management, ensuring that you achieve maximum value from your cloud investments. Our expertise lies in fostering cross-funct...

Hexaware Technologies
#1, Sector III, Millennium Business Park,, 'A' Block , TTC Industrial Estate, Mahape,, Navi Mumbai, Maharashtra, IN, 400710
Last Update: 17/08/2026
At Hexaware, we're not just a global technology and business process services company; we're a community of 31,600+ Hexawarians dedicated to one singular purpose: creating smiles through the power of great people and technology. With a presence in 58 offices across 28 c...
Compliance Ranges Comparison

Cortex Reply DE







Hexaware Technologies






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

Cortex Reply DE

Hexaware Technologies
FAQ
Latest Global CVEs
Pcapng file parser crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
X.509IF protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
H.245 protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
BUSMASTER file parser abnormal exit in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
Kerberos protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service