CVE-2026-3609

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-11. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Wellbia's XIGNCODE3 xhunter1.sys kernel driver, version 10.0.10011.16384 through 2023.12.7.78, privilege escalation vulnerability provides access to the IRP_MJ_WRITE command interface, which allows any user process to request a PROCESS_ALL_ACCESS. Note: KVE 2023-5589 (https://krcert.or.kr) was initially issued for version 10.0.10011.16384, but the vulnerability was not fully remediated and remains in version 2023.12.7.78.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

May 11, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

CVE-2026-3609: PPL-Bypassing Handle Leak in XIGNCODE3 (xhunter1.sys) | BlackSnufkin

https://blacksnufkin.github.io/posts/AntiCheat-LPE-CVE-2026-3609/

Vendor Advisories for CVE-2026-3609(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 217 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-23 18:38 UTCEG score recompute
  21. 2026-08-23 18:38 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 11:10 UTCEG score recompute
  3. 2026-08-17 11:10 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 04:25 UTCEG score recompute
  6. 2026-08-16 04:25 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-15 01:09 UTCGHSA enrichment
  10. 2026-08-14 14:03 UTCGHSA enrichment
  11. 2026-08-14 02:58 UTCEG score recompute
  12. 2026-08-14 02:58 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 03:35 UTCGHSA enrichment
  15. 2026-08-12 16:30 UTCEG score recompute
  16. 2026-08-12 16:30 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 15:47 UTCEG score recompute
  19. 2026-08-11 15:46 UTCGHSA enrichment
  20. 2026-08-11 13:43 UTCEPSS rescore
  21. 2026-08-11 01:10 UTCEG score recompute
  22. 2026-08-11 01:10 UTCGHSA enrichment
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 11:33 UTCGHSA enrichment
  25. 2026-08-10 00:25 UTCEG score recompute
  26. 2026-08-10 00:25 UTCGHSA enrichment
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 13:20 UTCGHSA enrichment
  29. 2026-08-09 02:15 UTCEG score recompute
  30. 2026-08-09 02:15 UTCGHSA enrichment
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 11:23 UTCGHSA enrichment
  33. 2026-08-08 00:18 UTCEG score recompute
  34. 2026-08-08 00:18 UTCGHSA enrichment
  35. 2026-08-07 13:12 UTCGHSA enrichment
  36. 2026-08-07 02:06 UTCGHSA enrichment
  37. 2026-08-06 15:01 UTCEG score recompute
  38. 2026-08-06 15:01 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-06 03:38 UTCEG score recompute
  41. 2026-08-06 03:38 UTCGHSA enrichment
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-05 16:32 UTCGHSA enrichment
  44. 2026-08-05 16:13 UTCEG score recompute
  45. 2026-08-05 16:13 UTCGHSA enrichment
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:38 UTCEPSS rescore
  48. 2026-08-03 19:26 UTCEG score recompute
  49. 2026-08-03 19:26 UTCGHSA enrichment
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-03 00:38 UTCGHSA enrichment
  52. 2026-08-02 13:12 UTCEG score recompute
  53. 2026-08-02 13:12 UTCGHSA enrichment
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-02 02:06 UTCEG score recompute
  56. 2026-08-02 02:06 UTCGHSA enrichment
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-27 14:13 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-25 14:18 UTCEPSS rescore
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-24 14:17 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 14:18 UTCEPSS rescore
  69. 2026-07-23 03:10 UTCEG score recompute
  70. 2026-07-22 14:08 UTCEPSS rescore
  71. 2026-07-21 15:24 UTCEPSS rescore
  72. 2026-07-20 17:08 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-19 02:29 UTCEPSS rescore
  75. 2026-07-18 10:04 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCBlackSnufkin/CredsHunter
    First seen May 12, 2026

    PoC for CVE-2026-3609 - XIGNCODE3 xhunter1.sys handle leak enabling PPL bypass and LSASS dumping

    Open source ↗
  • GitHub PoCBlackSnufkin/BYOVD
    First seen Dec 5, 2023

    BYOVD research use cases featuring vulnerable driver discovery and reverse engineering methodology. (CVE-2025-52915, CVE-2025-1055, CVE-2026-3609).

    Open source ↗

Frequently asked(5)

What is CVE-2026-3609?
CVE-2026-3609 is a high vulnerability published on May 11, 2026. Wellbia's XIGNCODE3 xhunter1.sys kernel driver, version 10.0.10011.16384 through 2023.12.7.78, privilege escalation vulnerability provides access to the IRPMJWRITE command interface, which allows any user process to request a PROCESSALLACCESS. Note: KVE 2023-5589 (https://krcert.or.kr) was…
When was CVE-2026-3609 disclosed?
CVE-2026-3609 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3609 actively exploited?
CVE-2026-3609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.9% of all scored CVEs.
What is the CVSS score of CVE-2026-3609?
CVE-2026-3609 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-3609?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3609, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3609

Explore →

Is Your Infrastructure Affected by CVE-2026-3609?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs