Comparison Overview
Powerupcloud Technologies

Powerupcloud Technologies
1084, 4th Floor, 14th Main Road, 18th Cross Rd, Sector 3,, Bangalore, Karnataka, 560102, IN
Last Update: 04/04/2026
As a top-tier Partner with major public cloud platforms and an LTI company, from consulting through to compliance we blend the best of human and machine intelligence to offer organizations automated and scaleable paths to achieve true cloud innovation. Robust frameworks...

Globant
875 Howard St, San Francisco, 94103, US
Last Update: 02/04/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

Powerupcloud Technologies







Globant






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Powerupcloud Technologies in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Globant in 2026.
Incident History - Powerupcloud Technologies (X = Date, Y = Severity)
Powerupcloud Technologies 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

Powerupcloud Technologies

Globant
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.