CVE-2025-46643VulnerabilityPublished 9 Jan 2026

CVE-2025-46643: Dell PowerProtect Data Domain with Data Domain Operating System (DD OS) Feature Release · Heap-based Buffer Overflow

Affects Dell PowerProtect Data Domain with Data Domain Operating System (DD OS) Feature ReleaseSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low : upgrade to 8.5.0.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.5.0.0, 8.3.1.20, 7.13.1.50 +1

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
DellPowerProtect Data Domain with Data Domain Operating System (DD OS) Feature Release	Affected >=7.7.1.0 <8.5.0.0	Fixed in 8.5.0.0
DellPowerProtect Data Domain with Data Domain Operating System (DD OS) LTS2025	Affected >=8.3.1.0 <8.3.1.20	Fixed in 8.3.1.20
DellPowerProtect Data Domain with Data Domain Operating System (DD OS) LTS2024	Affected >=7.13.1.0 <7.13.1.50	Fixed in 7.13.1.50
DellPowerProtect Data Domain with Data Domain Operating System (DD OS) LTS2023	Affected >=7.10.1.0 <7.10.1.80	Fixed in 7.10.1.80

AI-suggested

1. Monitor Dell’s official security advisories and apply patches or firmware updates promptly once released to address CVE-2025-46643. 2. Restrict local administrative access to Dell PowerProtect Data Domain systems to trusted personnel only, employing strict access controls and multi-factor authentication where possible. 3. Implement robust logging and monitoring of administrative activities on these systems to detect any unauthorized or suspicious access attempts. 4. Conduct regular security audits and vulnerability assessments on backup infrastructure to identify and remediate privilege escalation risks. 5. Employ network segmentation to isolate backup systems from general user environments, reducing the risk of local exploitation. 6. Develop and test incident response plans specifically for backup system outages to minimize downtime impact. 7. Educate system administrators about the risks of heap-based buffer overflows and the importance of applying security updates promptly. 8. Consider deploying host-based intrusion detection systems (HIDS) on backup servers to detect anomalous behavior indicative of exploitation attempts.

Description

Dell PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release versions 7.7.1.0 through 8.4.0.0, LTS2025 release version 8.3.1.10, LTS2024 release versions 7.13.1.0 through 7.13.1.40, LTS 2023 release versions 7.10.1.0 through 7.10.1.70, contain a Heap-based Buffer Overflow vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Denial of service.

Impact

For European organizations, the primary impact of CVE-2025-46643 is the potential denial of service on critical backup infrastructure. Dell PowerProtect Data Domain systems are integral to data protection strategies, and disruption could delay backup or restore operations, affecting business continuity and compliance with data retention policies. While confidentiality and integrity are not directly compromised, availability loss in backup systems can indirectly increase risk exposure. Organizations relying heavily on these systems for regulatory compliance, such as those in finance, healthcare, and government sectors, may face operational and reputational risks if backups become unavailable. The requirement for local high privilege access limits the attack surface, but insider threats or compromised administrative accounts could exploit this vulnerability. Given the low CVSS score, the immediate risk is moderate, but the criticality of backup systems elevates the operational impact. European entities with complex IT environments and strict uptime requirements should prioritize monitoring and mitigation to prevent service interruptions.

CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

dell.com/support/kbdoc/en-us/000405813/dsa-2025-415-security-update-for-dell-powerprotect-data-domain-multiple-vulnerabilities (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 16:33 UTC

WeaknessesCWE-122

Technical details

References

Community reviews

Related threats