Comparison Overview
Mahindra Lifespace Developers Ltd.

Mahindra Lifespace Developers Ltd.
Mahindra Lifespace Developers Ltd., Mumbai, 400018, IN
Last Update: 08/02/2026
About Mahindra Lifespace Developers Ltd. Established in 1994, Mahindra Lifespace Developers Ltd. (‘Mahindra Lifespaces’) brings the Mahindra Group’s philosophy of ‘Rise’ to India’s real estate and infrastructure industry through thriving residential communities and en...

International Workplace Group plc
Dammstrasse 19, Zug, Switzerland, CH, CH-6300
Last Update: 02/04/2026
IWG: the world’s leading platform for work, revolutionising how and where people work IWG (International Workplace Group) is the global leader in hybrid and platform working. With 4,000+ locations across 120 countries and millions of customers worldwide, IWG empowers bu...
Compliance Ranges Comparison

Mahindra Lifespace Developers Ltd.







International Workplace Group plc






Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Mahindra Lifespace Developers Ltd. in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for International Workplace Group plc in 2026.
Incident History - Mahindra Lifespace Developers Ltd. (X = Date, Y = Severity)
Mahindra Lifespace Developers Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Workplace Group plc (X = Date, Y = Severity)
International Workplace Group plc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mahindra Lifespace Developers Ltd.

International Workplace Group plc
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.