Local privilege escalation via insecure folder permissions

published 2026-11-09 2d ago modified 2026-11-10 yesterday also EUVD-2026-120462

cvss: 7.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits: 0; none known

Incorrect permission assignment allows local privilege escalation to SYSTEM on affected releases of the Illumio VEN for Windows. Code execution as NT AUTHORITY\LOCAL SERVICE on the Windows host is required to exploit this vulnerability. The flaw exists within the VEN installer, which grants LOCAL SERVICE full access to the VEN data and installation folders, whose configuration and state files are read and trusted by the SYSTEM-privileged illumio-ven-ctl component. An attacker can leverage this vulnerability to modify the VEN configuration so that illumio-ven-ctl executes an injected command in the context of the SYSTEM account.

Patch / fix

fixed in 1

Illumio Core Ven 23.2.22-LA-S1, 23.2.22-S1, 23.2.23-S1, 23.2.24-LA-S1, 23.2.24-S1, 23.2.30-S1, 23.2.31-LA-S1, 23.2.31-S1, 24.2.10-S1, 24.2.11-S1, 24.2.20-S1, 24.2.30-S1, 24.2.35-S1, 24.2.40-S1, 25.2.10-S1, 25.2.20-S1, 25.2.31-S1, 25.2.40-S1, 25.2.41-S1, 26.2.12-S1

Is CVE-2026-114031 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Illumio Core Ven

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource

References

product-docs-repo.illumio.com /Tech-Docs/Security+Advisories/out/en/security-advisories/insecure-folder-permissions-in-the-windows-ven.html
vendor-advisory

Sources

CVE List CVE-2026-114031
NVD CVE-2026-114031

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.