CVE-2026-22769 is a critical (CVSS 10.0) zero-day in Dell RecoverPoint for VMs caused by hard-coded firmware credentials, exploited since mid-2024 by the China-nexus group UNC6201 to bypass authentication and access backup appliances.
Organizations using Dell RecoverPoint for VMs for backup and disaster recovery in virtualized environments.
Hard-coded credentials grant full authentication bypass to appliances with broad access to production and replication datastores, enabling backup manipulation and data exfiltration.
- Apply Dell's emergency patches for RecoverPoint immediately.
- Restrict and segment network access to RecoverPoint appliances.
- Audit appliance authentication and configuration-change logs for anomalies.
- Rotate credentials and review backup policy integrity.
Key Technical Findings
Hard-coded-credential authentication bypass (CVE-2026-22769) in Dell RecoverPoint for VMs; CVSS 10.0; exploited by UNC6201 (China-nexus).
Dell RecoverPoint for VMs appliances and the datastores they access.
Use of hard-coded firmware credentials to bypass authentication.
Payloads executed to manipulate backup configurations.
Backdoor mechanisms established to maintain access.
Access leveraged to escalate within the network.
Techniques used to avoid detection.
Static credentials enable further credential access.
Pivoting to other systems via compromised credentials.
Sensitive data collected from backup repositories and exfiltrated.
Critical – full appliance compromise and access to backups/datastores.
Technical Background
The flaw is a set of hard-coded credentials embedded in RecoverPoint appliance firmware, allowing any attacker with network access to authenticate as a privileged user – a CVSS 10.0 condition. Because backup/replication appliances have broad reach into production and replication datastores, compromise enables backup tampering, policy disablement, and large-scale data theft.
UNC6201 reportedly used this for persistent footholds since mid-2024 before public disclosure and Dell’s February 2026 emergency patches. Patching, segmentation, and rigorous appliance log review are the priority controls.
Attack Chain Analysis
-
Initial Access
ActivityAuthenticate using hard-coded firmware credentials.
EvidenceLogins to the appliance from unusual sources.
TelemetryAppliance auth logs, network logs.
Detection opportunityAlert on unexpected appliance authentications.
-
Execution
ActivityManipulate backup configurations/policies.
EvidenceUnauthorized configuration changes.
TelemetryAppliance audit logs.
Detection opportunityMonitor for backup-policy/config changes.
-
Persistence
ActivityEstablish backdoor access.
EvidenceNew accounts or persistence on the appliance.
TelemetryAppliance audit logs.
Detection opportunityDetect new admin access or persistence.
-
Lateral Movement
ActivityPivot to other systems and datastores.
EvidenceUnexpected connections from the appliance.
TelemetryNetflow, firewall logs.
Detection opportunityBaseline and alert on new flows from the appliance.
-
Exfiltration
ActivityExfiltrate data from backup repositories.
EvidenceOutbound volume anomalies.
TelemetryProxy/firewall logs.
Detection opportunityDetect egress spikes from backup infrastructure.
Deep Technical Behavior Analysis
The decisive characteristic is that no exploit chain is needed – static credentials provide direct privileged access. The most consequential behaviors are backup-configuration tampering (which can defeat recovery) and exfiltration from repositories that aggregate sensitive data. Appliance audit logs and segmentation are therefore critical, since endpoint EDR does not cover the appliance.
Specific indicators and post-exploitation tooling beyond what is described are not specified in the source material and require validation.
Indicators of Compromise
Indicators of Behavior
Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).
| Behavioral Indicator | Description | Data Source | Confidence |
|---|---|---|---|
| Anomalous PowerShell execution | Encoded/obfuscated commands, download cradles, or unusual parent-child process lineage. | Sysmon EID 1, PowerShell 4104 | Potential |
| Suspicious child process lineage | Office or web/service processes spawning script hosts or shells. | Sysmon EID 1, EDR | Potential |
| Security log clearing | Event log cleared or audit policy changed to hinder visibility. | Windows Security 1102, 4719 | Potential |
| New service / scheduled task creation | Unexpected persistence via services or tasks. | Security 7045, 4698; Sysmon | Potential |
| Beaconing to rare destinations | Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. | Proxy, firewall, DNS logs | Potential |
| Unusual DNS queries | High-entropy or rare domains; possible tunneling. | DNS resolver logs | Potential |
| Authentication anomalies | Spraying/stuffing, impossible travel, or MFA fatigue patterns. | IdP/VPN logs, Azure AD/Okta sign-ins | Potential |
Detection Engineering Guidance
Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.
Recommended Log Sources
| Platform | Log Source | What to Look For | Priority |
|---|---|---|---|
| Windows | Security Event Log | Logon (4624/4625), service (7045), task (4698), log clear (1102) | High |
| Windows | Sysmon | Process creation (1), network (3), image load (7), LSASS access (10) | High |
| Windows | PowerShell Operational | Script block logging (4104), module logging | High |
| Endpoint | EDR / Defender telemetry | Process tree, persistence, tamper attempts | High |
| Identity | IdP / VPN logs | Impossible travel, spraying, MFA fatigue | High |
| Network | DNS resolver logs | Rare/high-entropy domains, tunneling | Medium |
| Network | Proxy / firewall logs | Beaconing, direct-IP C2, exfil volume | High |
MITRE ATT&CK Mapping
Not specified in the source material. Map techniques from confirmed telemetry before operationalising.
Incident Response Guidance
- Validate exposure and confirm whether the issue applies to your environment.
- Preserve evidence (memory, disk, relevant logs) before remediation.
- Isolate affected hosts/accounts if compromise is suspected.
- Collect volatile data and review the log sources listed above.
- Hunt for the indicators of behavior and any related atomic indicators.
- Rotate potentially exposed credentials, keys, and session tokens.
- Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
- Patch affected systems; reimage where integrity cannot be assured.
- Run post-remediation validation and a BAS/security-validation retest.
Remediation and Hardening
- Patch affected systems and reduce internet-exposed services.
- Enforce MFA and least-privilege for privileged and remote access.
- Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
- Restrict script execution and constrain LOLBins where feasible.
- Monitor persistence locations and disable unnecessary services.
- Segment critical assets and review privileged accounts.
- Rotate secrets and remove credentials from configuration files.
- Tune SIEM/EDR detections, then validate controls after changes.
Business Risk
- Service disruption: degraded or unavailable systems during compromise or recovery.
- Data exposure: risk to sensitive, regulated, or customer data depending on scope.
- Regulatory exposure: potential breach-notification and compliance obligations.
- Financial impact: incident response, downtime, and potential extortion costs.
- Brand and trust impact: reputational damage with customers and partners.
- Identity blast radius: compromised accounts can expand access across cloud and SaaS.
Executive Takeaway
What leadership needs to know: Hard-coded credentials grant full authentication bypass to appliances with broad access to production and replication datastores, enabling backup manipulation and data exfiltration. Current assessed risk: Critical.
Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.
Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.
Validating Your Defenses with Valitrix
The Valitrix Breach and Attack Simulation (BAS) platform provides organizations with a powerful toolset for validating their security controls against real-world adversary techniques mapped to the MITRE ATT&CK framework. By safely emulating specific techniques associated with CVE-2026-22769, Valitrix enables security teams to assess their detection and prevention capabilities effectively.
This proactive approach allows organizations to not only identify gaps in their defenses but also prioritize remediation efforts based on real-time insights. Teams can simulate scenarios where attackers exploit hard-coded credentials, providing valuable data on how well current security measures withstand sophisticated attacks.
Key Takeaways
- CVE-2026-22769 is a critical zero-day vulnerability in Dell RecoverPoint, requiring immediate attention from security teams.
- The vulnerability is actively exploited by UNC6201, targeting data integrity across multiple sectors.
- A robust detection strategy utilizing EDR, Sysmon logs, and network traffic analysis is essential for early identification of exploits.
- Patching and credential rotation are vital steps in mitigating the risks associated with this vulnerability.
Frequently Asked Questions
What is CVE-2026-22769?
CVE-2026-22769 is a zero-day vulnerability in Dell RecoverPoint that allows unauthorized access via hard-coded credentials embedded in firmware.



