Threats / Dell / CVE-2026-22769
CVE-2026-22769
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Dell RecoverPoint for Virtual Machines (RP4VMs) vulnerability
Dell RecoverPoint for Virtual Machines contains hard-coded credentials allowing unauthenticated remote attackers to gain unauthorized OS and root-level access.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can exploit hard-coded credentials in RP4VMs to obtain root-level persistence on the underlying operating system, enabling full system compromise and data access.
CISA KEV Yes · 2026-02-185EPSS 0.13122 (verify live)6CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-18).
Probability (EPSS)
EPSS 0.13122 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Dell, RecoverPoint for Virtual Machines (RP4VMs). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-798 Hard-coded Credentials — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I discover or obtain the hard-coded credentials embedded in the RP4VMs application.
Business
Credential exposure represents a fundamental authentication bypass that eliminates access controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use these credentials to authenticate remotely to the RP4VMs system without legitimate user credentials.
Business
Unauthorized remote access bypasses identity verification and grants attacker entry to critical backup infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges to root level on the underlying operating system.
Business
Root-level compromise enables complete system control, including modification of recovery data and backup integrity.
4
Data at risk — exfiltration narrative 4
Attacker
I establish persistent access mechanisms to maintain control across system restarts and updates.
Business
Persistent root access allows long-term data exfiltration, ransomware staging, and lateral movement to protected environments.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by dellCNA
Credited with finding itDell would like to thank Peter Ukhanov from Google/Mandiant for reporting this issue.finder