Comparison Overview
Sumitomo Electric Fusion Splicer

Sumitomo Electric Fusion Splicer
1-3-13 Motoakasaka, , Minato-ku, 107-8468, JP
Last Update: 02/04/2026
A Sumitomo Electric's fusion splicer is the ideal choice for increasing splicing efficiency in the field. From the core network to the last mile of FTTx networks, there’s a Sumitomo Electric fusion splicer that fits any application. Our service and maintenance providers...

Cox Communications
6205 Peachtree Dunwoody Road, Atlanta, 30328, US
Last Update: 01/04/2026
Cox Communications is committed to creating more moments of real human connection. We bring people closer to family and friends through technology that’s inspired by a culture that puts people first, and we’re always working to improve life in the communities we serve. ...
Compliance Ranges Comparison

Sumitomo Electric Fusion Splicer







Cox Communications






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Sumitomo Electric Fusion Splicer in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Cox Communications in 2026.
Incident History - Sumitomo Electric Fusion Splicer (X = Date, Y = Severity)
Sumitomo Electric Fusion Splicer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cox Communications (X = Date, Y = Severity)
Cox Communications cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sumitomo Electric Fusion Splicer

Cox Communications
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.