CVE-2026-61407

Published

18 August 2026

Modified

20 August 2026

CVSS Score v3.1 8.8

Click a component to see what it means

Raw vector

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

EPSS Score 0.0010 1th percentile

Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2026-61407 is a high-severity EAR (CWE-698) vulnerability in Dell Watchdog Timer Driver (inferred from references). Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 1th 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-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-60940

Vulnerability Data

Dell Watchdog Timer Driver versions prior to 2.0.0.1 contain an Exposed IOCTL with Insufficient Access Control vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Privilege Escalation.

CWE(s): CWE-698

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-2572Shared CWE-698

CVE-2024-2569Shared CWE-698

CVE-2026-16323Shared CWE-698

CVE-2024-2571Shared CWE-698

CVE-2025-6967Shared CWE-698

CVE-2025-53077Shared CWE-698

CVE-2024-2635Shared CWE-698

CVE-2024-2573Shared CWE-698

CVE-2024-2570Shared CWE-698

CVE-2024-48766Shared CWE-698

Affected Assets

Dell

Watchdog Timer Driver

inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover execution paths that continue after a redirect.

AC-3 Access Enforcement partial match

Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.

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.PS-06 mostly match

prevents

Secure SDLC practices directly prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.

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.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect EAR flaws before deployment.

A.8.25 Secure development life cycle partial match

prevents

Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.

A.8.26 Application security requirements partial match

prevents

Application security requirements can mandate safe redirect patterns and post-redirect termination.

A.8.27 Secure system architecture and engineering principles partial match

prevents

Secure architecture principles discourage continued execution after redirects.