Quick answers
- Is CVE-2026-6423 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6423 being exploited in the wild.
- How severe is CVE-2026-6423?
- Informational severity, with a CVSS score of 8.5, published 16 July 2026.
- Which products and versions are affected?
- Eset Inspect Connector 3.0.5775.0 and earlier.
- Is there a fix for CVE-2026-6423?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6423 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-6423?
- Check whether you run Eset Inspect Connector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A local privilege escalation vulnerability exists in ESET Inspect Connector for Windows (versions 3.0.5775.0 and earlier) due to improper authentication and origin validation within an Advanced Local Procedure Call (ALPC) interface. An attacker with low-privileged local access can send specially crafted ALPC requests to the vulnerable process. Because the Inter-Process Communication (IPC) channel fails to verify the identity of the sender, the process accepts these messages, allowing the attacker to execute restricted functionality with the higher privileges of the ESET service. The issue is addressed in ESET Inspect Connector version 3.1.6017.0 and later.
Affected products
- ESET Inspect Connector 3.0.5775.0 and earlier
Timeline
- 2026-07-14: advisory: Initial advisory released by ESET
- 2026-07-16: disclosed: CVE published to NVD dataset