Cyber Resilience

CVE-2026-49499

Dell Powerprotect Data Manager ≤ 20.2

Published
22 July 2026
Modified
29 July 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2026-49499 is a high-severity Generation of Incorrect Security Tokens (CWE-1270) vulnerability in Dell Powerprotect Data Manager. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Dell PowerProtect Data Manager, versions prior to 20.2.0.0, contain(s) a Generation of Incorrect Security Tokens vulnerability in the IAM. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Elevation of privileges.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
T1606.002 SAML Tokens Credential Access
An adversary may forge SAML tokens with any permissions claims and lifetimes if they possess a valid SAML token-signing certificate.
T1134 Access Token Manipulation Stealth
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls.
T1550 Use Alternate Authentication Material Lateral Movement
Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-43725Same product: Dell Powerprotect Data Manager
CVE-2025-43886Same product: Dell Powerprotect Data Manager
CVE-2024-22454Same product: Dell Powerprotect Data Manager
CVE-2026-22269Same product: Dell Powerprotect Data Manager
CVE-2025-23375Same product: Dell Powerprotect Data Manager
CVE-2026-40712Same product: Dell Powerprotect Data Manager
CVE-2026-22266Same product: Dell Powerprotect Data Manager
CVE-2026-22268Same product: Dell Powerprotect Data Manager
CVE-2024-22445Same product: Dell Powerprotect Data Manager
CVE-2023-28062Same product: Dell Powerprotect Data Manager

Affected Assets

dell
powerprotect data manager
≤ 20.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover flaws that produce incorrect security tokens before deployment.

Correct association and handling of security attributes directly governs generation of valid tokens used for authorization decisions.

Requiring documented, secure development processes and tools reduces the chance of implementing faulty token-generation logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-04 mostly match
degrades

Verification of identity assertions can detect incorrect tokens but does not prevent flawed generation logic.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly reduce the chance of implementing incorrect token generation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect incorrect token generation before deployment.

prevents

Proper use of cryptography ensures tokens are generated with correct algorithms, keys and entropy.

prevents

Secure development lifecycle practices include requirements and reviews that prevent flawed token-generation logic.

prevents

Application security requirements explicitly call for correct token issuance and validation mechanisms.

prevents

Secure coding standards reduce the likelihood of implementation errors that produce incorrect tokens.

prevents

Secure authentication mechanisms directly govern the correct generation and validation of security tokens.

References