CVE-2026-0539
Local privilege escalation via pcvisit Windows service binary.
Is CVE-2026-0539 being exploited?
Not confirmed. CVE-2026-0539 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.10% probability of exploitation in the next 30 days.
How severe is CVE-2026-0539?
CVE-2026-0539 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-0539?
Yes. A fix has been recorded for CVE-2026-0539. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0539 affect?
CVE-2026-0539 affects pcvisit Windows service (Windows). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0539?
Update to version 25.12.3.1745 or newer.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-privilege local users can overwrite the service binary and run as NT SYSTEM on boot, enabling full system compromise.
Patch when possible
- affected>= 22.6.22.1329 and < 25.12.3.1745
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.