Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8 CISA Known Exploited Vulnerability

CVE-2024-8069

Citrix Session Recording Deserialization of Untrusted Data Vulnerability

Citrix Session Recording

Limited remote code execution with privilege of a NetworkService Account access in Citrix Session Recording if the attacker is an authenticated user on the same intranet as the session recording server

CVSS
8
HIGH
EPSS
18.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
12 Nov 2024
CWE-502

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 25 August 2025. US federal agencies were required to remediate it by 15 September 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 18.2%, which is higher than 97.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2024-8069 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2024-8069.

What does CVE-2024-8069 affect?

CVE-2024-8069 affects Citrix Session Recording. Limited remote code execution with privilege of a NetworkService Account access in Citrix Session Recording if the attacker is an authenticated user on the same intranet as the session recording server

How severe is CVE-2024-8069?

CVE-2024-8069 is rated HIGH with a CVSS base score of 8. EPSS puts the probability of exploitation in the next 30 days at 18.2%, higher than 97.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 September 2025.

How should organisations respond to CVE-2024-8069?

Apply the vendor patch for Citrix Session Recording as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.