Comparison Overview
SecurityX
SecurityX
N/A
Last Update: 01/08/2026
Globant
875 Howard St, San Francisco, 94103, US
Last Update: 09/09/2026
At Globant, we create the digitally-native products that people love. We bridge the gap between businesses and consumers through technology and creativity, leveraging our experience as an AI powerhouse. We dare to digitally transform organizations and strive to delight ...
Compliance Ranges Comparison
SecurityX
Globant
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for SecurityX in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Globant in 2026.
Incident History - SecurityX (X = Date, Y = Severity)
SecurityX cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Globant (X = Date, Y = Severity)
Globant cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SecurityX
Globant
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.