What is CVE-2024-8069?

CVE-2024-8069 is Limited remote code execution with privilege of a NetworkService Account access. The supplied enrichment data classifies it as Deserialization mapped to CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

14 public PoC repositories reported; 3 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-8069 using CVSS 8, EPSS 15%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Void Rabisu (), RomCom (), Returned Libra (), Hacking Team (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighDeserializationpublic exploit

CVE-2024-8069

CVE-2024-8069 — Limited remote code execution with privilege of a NetworkService Account access

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-8069 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Nov 12, 2024Updated Jun 17, 2026Sources: NVD, Citrix Session Recording (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 25, 2025

EPSS

15%

ahead of 97% of scored CVEs

Affects

Citrix Session Recording

4 products listed

CVSS base

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Citrix Session Recording to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Sep 15, 2025 — passed 376 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Citrix Session Recording	Citrix Session Recording	2407 Current Release to < 24.5.200.8	Vulnerable
Citrix Session Recording	Citrix Session Recording	1912 LTSR	Vulnerable
Citrix Session Recording	Citrix Session Recording	2203 LTSR	Vulnerable
Citrix Session Recording	Citrix Session Recording	2402 LTSR	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Adjacent

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8	CVSS 3.1	high	2.1	5.9	NVD
5.1	CVSS 4.0	medium	—	—	Citrix Session Recording (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-502 · Deserialization of Untrusted Data

Modify Application Data
Unexpected State
DoS: Resource Consumption (CPU)
Varies by Context

Mitigation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.

CWE-94 · Improper Control of Generation of Code ('Code Injection')

Bypass Protection Mechanism
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands
Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

Weakness & attack patterns

CWE-502Deserialization of Untrusted Data

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-586 · Object Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 25, 2025

Federal deadline

Sep 15, 2025

passed 376 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

3 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 14 public PoC repositories were reported.

EDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Void RabisuRomComReturned LibraHacking Team

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.0 (AV:A)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Aug 27, 2025 · SOCRadar CTI
Cve is exploited Citrix Session Recording Deserialization of Untrusted Data Vulnerability
Aug 26, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Aug 25, 2025 · CISA
2024
Initial · CVE published
Nov 12, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

15×SVRS was changedDec 1, 2024 – Sep 26, 2025 · SOCRadar CTI
9×ModifiedAug 25, 2025 – Oct 24, 2025 · SOCRadar CTI
2×TweetsAug 26, 2025 – Aug 27, 2025 · SOCRadar CTI
1×Github_Repos · Github repository created, HORKimhab/CVE-2024-8068-CVE-2024-8069Aug 19, 2026 · SOCRadar CTI

References

4 on the record

support.citrix.com/s/article/CTX691941-citrix-session-recording-security-bulletin-for-cve20248068-and-cve20248069?language=en_US
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-8069
US Government Resource
support.citrix.com/external/article/691941/citrix-session-recording-security-bullet.html
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2024-8069
Vendor Advisory

Coverage

6 stories from the feeds we poll

1 more reports on this CVEShowing 5 of 6 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Citrix Session Recordingevery CVE for this vendor
August 2025what else CISA listed
Deserializationsame class
CWE-502other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-8069 is Limited remote code execution with privilege of a NetworkService Account access, a high vulnerability affecting Citrix Session Recording from Citrix Session Recording. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 14 public PoC repositories reported; 3 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8 describes technical severity, while EPSS 15% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.