Comparison Overview
Sainsbury's Digital, Tech and Data
Sainsbury's Digital, Tech and Data
33 Holborn, London, EC1N 2HT, GB
Last Update: 25/03/2026
Our tech team plays a vital role in supporting Sainsbury’s mission and strategy for the future. We power the UK’s third-busiest retail site, and our innovations allow our customers to shop and connect with us whenever they want to, reliably and safely, and help our coll...
RD Saúde
Avenida Corifeu de Azevedo Marques 3097, São Paulo, BR
Last Update: 02/04/2026
Somos a RD Saúde, um ecossistema de saúde integral, com mais de 3 mil farmácias em todo o Brasil e negócios em saúde que dividem o mesmo propósito: contribuir para uma sociedade mais saudável. Nossa jornada começou em novembro de 2011, fruto da união entre Droga Raia e ...
Compliance Ranges Comparison
Sainsbury's Digital, Tech and Data
RD Saúde
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Sainsbury's Digital, Tech and Data in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for RD Saúde in 2026.
Incident History - Sainsbury's Digital, Tech and Data (X = Date, Y = Severity)
Sainsbury's Digital, Tech and Data cyber incidents detection timeline including parent company and subsidiaries.
Incident History - RD Saúde (X = Date, Y = Severity)
RD Saúde cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sainsbury's Digital, Tech and Data
RD Saúde
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)