Comparison Overview
Nexi Digital

Nexi Digital
Corso Sempione, 57, Milan, IT
Last Update: 12/03/2026
NEXI Digital is a joint venture between Reply and Nexi Group. It provides cutting-edge digital solutions for Nexi Group, The European PayTech. We master modern technologies and agile methodologies, collaborating with Nexi Group to contribute to the success of all busine...

Fifth Third Bank
38 Fountain Square Plaza, Cincinnati, 45202, US
Last Update: 02/04/2026
At Fifth Third Bank, everything we do is rooted in our purpose: to improve the lives of our customers and the well-being of our communities. Since our founding in 1858, we’ve been committed to creating a better financial experience by empowering our customers and client...
Compliance Ranges Comparison

Nexi Digital







Fifth Third Bank






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Nexi Digital in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Fifth Third Bank in 2026.
Incident History - Nexi Digital (X = Date, Y = Severity)
Nexi Digital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fifth Third Bank (X = Date, Y = Severity)
Fifth Third Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Nexi Digital

Fifth Third Bank
FAQ
Latest Global CVEs
Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.
- https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834
- https://github.com/v12-security/pocs/tree/main/redis/server_ssl
- https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES
Unrestricted Upload of File with Dangerous Type in the product photo upload in Roskus Prospero Flow CRM before 5.16.0 allows an authenticated user holding the create product permission (routine Seller role) to execute arbitrary JavaScript in the application origin. The photo validation rule classifies the file only by its content (magic bytes) and rejects only a fixed list of PHP extensions, while ProductSaveController::save() names the stored file using the client-supplied extension and copies it into the public web root. A file that begins with an image header and carries an HTML extension passes validation, is stored under public/asset/upload/product/, and is served with a text/html content type, turning the upload into first-party stored script execution.
A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4
A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgrade to the version 0.24 or later.
A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.