LiveActive security incident?Get immediate response
CVE Record

CVE-2026-68771: ComfyUI 0.23.0 Unauthenticated RCE via LoadTrainingDataset Pickle Deserialization

ComfyUI v0.23.0 contains an unsafe deserialization vulnerability in the LoadTrainingDataset node that allows unauthenticated remote attackers to execute arbitrary Python code by uploading a crafted pickle file and triggering its deserialization. Attackers can upload a malicious shard_*.pkl file via the unauthenticated POST /upload/image endpoint and then queue a workflow graph via POST /prompt referencing the uploaded file, causing torch.load to deserialize the attacker-controlled pickle payload using __reduce__ and execute arbitrary commands as the ComfyUI process user.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A network-accessible ComfyUI 0.23.0 instance could let an unauthenticated attacker run Python code with the service account’s permissions. Successful exploitation could expose models, credentials, workflows, and connected data, alter system contents, or interrupt service.

Executive priority

Treat internet-exposed or broadly reachable instances as an immediate remediation priority. Patch promptly, restrict access while remediation proceeds, and investigate exposed systems for misuse. Internal, authenticated deployments remain important but may be prioritized after externally reachable instances based on verified controls.

Technical view

The LoadTrainingDataset node unsafely deserializes attacker-controlled pickle data through torch.load. An attacker can reportedly upload a crafted shard file through the unauthenticated image-upload route and reference it in a queued workflow, producing remote code execution without credentials or user interaction.

Likely exposure

Highest risk applies to ComfyUI 0.23.0 deployments reachable by untrusted networks where upload and workflow-queueing endpoints are unauthenticated and LoadTrainingDataset is available. The bundle’s structured affected-version value is incomplete, so broader version exposure should be confirmed through vendor guidance.

Exploitation context

CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact. The bundle marks KEV false and provides no evidence of active exploitation; public exploit availability is not established here.

Researcher notes

The reported trust-boundary failure combines unauthenticated file upload, unauthenticated workflow submission, and unsafe pickle deserialization. The source bundle identifies a patch commit but no fixed release number. Its affected-version metadata lists “0,” conflicting with the 0.23.0 title; confirm exact version ranges with current vendor records.

Mitigation direction

  • Apply the vendor patch or upgrade to a release containing commit 94ee49b1612824366a8631ea069b2a1fa5c73720.
  • Until patched, prevent untrusted network access to ComfyUI and require authentication through a trusted access layer.
  • Restrict or disable affected upload, workflow-queueing, and LoadTrainingDataset functionality where operationally feasible.
  • Rotate credentials accessible to the ComfyUI process if investigation identifies suspicious activity or possible compromise.

Validation and detection

  • Inventory ComfyUI versions and identify deployments running 0.23.0 or otherwise lacking the cited patch.
  • Confirm whether upload and workflow-queueing routes are reachable without authentication from untrusted networks.
  • Verify the deployed code includes commit 94ee49b1612824366a8631ea069b2a1fa5c73720 or a vendor-confirmed equivalent fix.
  • Review logs for unexpected uploads, shard pickle files, queued LoadTrainingDataset workflows, and anomalous child processes.
  • Test access controls using benign requests only; do not upload serialized payloads to production systems.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-68771 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-68771Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Comfy-OrgComfyUI0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.