cve.bz

CVE-2026-105051 irdeto denuvo anti-tamper: Use of Less Trusted Source

1.9 lowEPSS 0.08%

Low (1.9) in irdeto denuvo anti-tamper. EPSS 0.08% estimated probability of exploitation activity in the next 30 days.

On this page
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).

Severity

CVSS 3.1

1.9 low
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS
0.08% (unchanged from 0.08% a week ago; 0.08% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-348 Use of Less Trusted Source
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105051 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105051?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105051?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105051 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • irdeto:denuvo anti-tamper

Versions

From the CNA's record in the CVE List.

ProductAffected
Irdeto Denuvo Anti-Tamperthrough 2026-03-04

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON