Dell PowerProtect Data Domain mit Data Domain Operating System (DD OS) der Feature Release Versionen 7.7.1.0 bis 8.5, LTS2025 Release Version 8.3.1.0 bis 8.3.1.20, LTS2024 Release Versionen 7.13

Successful exploitation of CVE-2026-23776 could allow an attacker to gain elevated privileges on a vulnerable Dell PowerProtect Data Domain system. This could lead to unauthorized access to sensitive data, modification of system configurations, or even complete control of the affected appliance. Given the critical nature of data stored on Data Domain systems, this vulnerability poses a significant risk to data confidentiality, integrity, and availability. The ability to escalate privileges from a low-privileged state significantly broadens the attack surface and increases the potential for widespread compromise within an organization’s data protection infrastructure. This vulnerability highlights the importance of robust certificate validation practices in all systems handling sensitive data.

Organizations heavily reliant on Dell PowerProtect Data Domain for data protection and disaster recovery are at significant risk. Specifically, environments with legacy DD OS versions (7.7.1.0–8.5) and those with less stringent certificate management practices are particularly vulnerable. Shared hosting environments utilizing Data Domain appliances also face increased risk due to the potential for cross-tenant exploitation.

• linux / server:

journalctl -u dd-authd -g 'certificate validation failed'

• linux / server:

ps aux | grep -i certificate_validation

• generic web:

curl -I <data_domain_ip>/login.jsp | grep 'Certificate-Transparent'

1. 2026-04-17Disclosure

   disclosure

1. Reserviert2026-01-16
2. Veröffentlicht2026-04-17
3. Geändert2026-04-20
4. EPSS aktualisiert2026-04-24

The primary mitigation for CVE-2026-23776 is to upgrade Dell PowerProtect Data Domain to version 8.6.0.0 or later, which contains the fix. If immediate upgrading is not possible, consider implementing stricter certificate validation policies on the network perimeter to prevent malicious certificates from being accepted. Review and strengthen existing certificate management practices, ensuring that only trusted certificates are used for authentication. While a direct workaround is not available, implementing network segmentation can limit the potential blast radius of a successful exploit. Monitor system logs for any unusual certificate-related activity. After upgrading, confirm the fix by attempting a login with a certificate that should be rejected by the updated system.