Quick answers
- Is CVE-2026-38763 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38763 being exploited in the wild.
- How severe is CVE-2026-38763?
- Informational severity, with a CVSS score of 6.2, published 22 July 2026.
- Which products and versions are affected?
- Unistal Systems Protegent 360 2.0.0.4.
- Is there a fix for CVE-2026-38763?
- 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-38763 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-38763?
- Check whether you run Unistal Systems Protegent 360 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 denial of service vulnerability exists in the Secure Folders driver (wscsrv.sys version 1.0.0.9) of Protegent 360 v2.0.0.4. The driver creates a device object (\Device\FE79F7D853E643089D51EDCDA79805C4) with no access control (CWE-732), allowing any unprivileged local user to send IOCTL requests. Specifically, the function sub_13828 fails to properly validate memory allocation results from ExAllocatePool, leading to a NULL pointer dereference (CWE-476) when the system is under memory pressure or provided with specific inputs. This results in a SYSTEM_SERVICE_EXCEPTION bug check (BSOD). No patch is currently confirmed, though the researcher suggests the vendor lacks basic access control checks across multiple driver components.
Affected products
- Unistal Systems Pvt. Ltd. Protegent 360 2.0.0.4
Timeline
- 2026-05-21: disclosed: Initial researcher disclosure by DreadSec
- 2026-07-22: advisory: CVE published to NVD