CVE-2024-14032

Twitch Studio broken access control

7.8 HIGHPublic exploitEPSS 0.18%

Published6 Apr 2026

Description

Twitch Studio version 0.114.8 and prior contain a privilege escalation vulnerability in its privileged helper tool that allows local attackers to execute arbitrary code as root by exploiting an unprotected XPC service. Attackers can invoke the installFromPath:toPath:withReply: method to overwrite system files and privileged binaries, achieving full system compromise. Twitch Studio was discontinued in May 2024.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Twitch Studio≤ 0.114.8

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://help.twitch.tv/s/article/recommended-software-for-broadcastingProduct
https://help.twitch.tv/s/topic/0TO3a000000kZfYGAU/twitch-studioProduct
https://www.iru.com/blog/twitch-privileged-helperExploitThird Party Advisory
https://www.vulncheck.com/advisories/twitch-studio-launcherhelper-xpc-missing-authorization-to-root-file-writeThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-14032 being actively exploited?

CVE-2024-14032 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.18%.

How severe is CVE-2024-14032?

CVE-2024-14032 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.18% probability of exploitation.

Which products are affected by CVE-2024-14032?

Affected products include Twitch Studio.

How do I fix CVE-2024-14032?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-14032 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.