CVE-2026-82671

LOWPre-NVD 3.43.4—
EchelonGraph scoreHIGH confidence

Score 3.4 from GitHub Security Advisory published 2026-08-31. a secondary CVSS source baseline 3.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.4Exploit: None knownExposed: 0

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

A vulnerability has been found in IObit Unlocker 1.3.0.12. This vulnerability affects the function ZwTerminateProcess in the library IObitUnlocker.sys of the component IRP_MJ_DEVICE_CONTROL Handler. The manipulation leads to improper privilege management. An attack has to be approached locally. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
3.4
EG Score
3.4(high)
EG Risk
15(Track)
EG Risk 15/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
Severity34% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 31, 2026

Last Modified

August 31, 2026

References (4)

Vendor Advisories for CVE-2026-82671(1)

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

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 23:59 UTCEG score recompute
  3. 2026-09-17 23:59 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:27 UTCEG score recompute
  7. 2026-09-15 03:27 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-12 07:20 UTCEG score recompute
  11. 2026-09-12 07:20 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-09 11:12 UTCEG score recompute
  15. 2026-09-09 11:12 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-06 15:04 UTCEG score recompute
  18. 2026-09-06 15:04 UTCGHSA enrichment
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-03 18:55 UTCEG score recompute
  22. 2026-09-03 18:54 UTCGHSA enrichment
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
Show 9 more
  1. 2026-08-31 22:21 UTCEG score recompute
  2. 2026-08-31 22:21 UTCGHSA enrichment
  3. 2026-08-31 22:15 UTCEG score recompute
  4. 2026-08-31 22:15 UTCGHSA enrichment
  5. 2026-08-31 21:02 UTCEG score recompute
  6. 2026-08-31 21:02 UTCGHSA enrichment
  7. 2026-08-31 10:18 UTCEG score recompute
  8. 2026-08-31 09:47 UTCEG score recompute
  9. 2026-08-31 09:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82671?
CVE-2026-82671 is a low vulnerability published on August 31, 2026. A vulnerability has been found in IObit Unlocker 1.3.0.12. This vulnerability affects the function ZwTerminateProcess in the library IObitUnlocker.sys of the component IRPMJDEVICE_CONTROL Handler. The manipulation leads to improper privilege management. An attack has to be approached locally. The…
When was CVE-2026-82671 disclosed?
CVE-2026-82671 was first published in the National Vulnerability Database on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82671 actively exploited?
CVE-2026-82671 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-82671?
CVE-2026-82671 has a CVSS v3 base score of 3.4 (NVD).
How do I remediate CVE-2026-82671?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82671, 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-82671

Explore →

Is Your Infrastructure Affected by CVE-2026-82671?

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

Start Free Scan →Browse All CVEs