Comparison Overview
IDVerse, part of LexisNexis® Risk Solutions

IDVerse, part of LexisNexis® Risk Solutions
London, GB
Last Update: 01/04/2026
IDVerse®, part of LexisNexis® Risk Solutions is a cutting-edge document authentication and biometric verification solution that helps you confidently approve trusted transactions while detecting deepfakes, GenAI and forged documents. Powered by state-of-the-art, propr...

Arrow Electronics
9201 East Dry Creek Road, Centennial, 80112, US
Last Update: 02/04/2026
Arrow Electronics (NYSE:ARW) guides innovation forward for thousands of leading technology manufacturers and service providers. With 2024 sales of $27.9 billion, Arrow develops technology solutions that help improve business and daily life. Our broad portfolio that spa...
Compliance Ranges Comparison

IDVerse, part of LexisNexis® Risk Solutions







Arrow Electronics






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for IDVerse, part of LexisNexis® Risk Solutions in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Arrow Electronics in 2026.
Incident History - IDVerse, part of LexisNexis® Risk Solutions (X = Date, Y = Severity)
IDVerse, part of LexisNexis® Risk Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Arrow Electronics (X = Date, Y = Severity)
Arrow Electronics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

IDVerse, part of LexisNexis® Risk Solutions

Arrow Electronics
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.