CVE-2025-67303VulnerabilityPublished 5 Jan 2026

CVE-2025-67303: ComfyUI-Manager · n/a

Affects ComfyUI-ManagerSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 3.38 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.38

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: evidence found.
nuclei template: ComfyUI-Manager < 3.38 - Configuration Overwrite
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade comfy-org/ComfyUI-Manager to 3.38.

Affected software

Product	Affected	Fixed in
GitHubcomfy-org/ComfyUI-Manager`pkg:github/comfy-org/ComfyUI-Manager`Other threats	Affected <3.38	Fixed in 3.38

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade ComfyUI-Manager to version 3.38 or later immediately once available, as this version addresses the vulnerability by securing file storage locations. 2. Restrict access to the ComfyUI-Manager web interface using network segmentation, VPNs, or IP whitelisting to limit exposure to trusted users only. 3. Implement strict file system permissions on servers hosting ComfyUI-Manager to ensure configuration files are not accessible via the web server or unauthorized users. 4. Conduct regular audits of web interface access logs and file permissions to detect unauthorized access attempts or misconfigurations. 5. Employ web application firewalls (WAFs) to monitor and block suspicious requests targeting the management interface. 6. Educate system administrators about the risks of exposing management interfaces and enforce secure configuration management practices. 7. Monitor threat intelligence sources for any emerging exploits related to CVE-2025-67303 and apply patches or mitigations promptly. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous activity targeting ComfyUI-Manager.

Description

An issue in ComfyUI-Manager prior to version 3.38 allowed remote attackers to potentially manipulate its configuration and critical data. This was due to the application storing its files in an insufficiently protected location that was accessible via the web interface

Impact

For European organizations, exploitation of CVE-2025-67303 could lead to unauthorized modification or disclosure of configuration data, undermining system integrity and confidentiality. This may result in operational disruptions, data breaches, or further compromise of internal systems if attackers manipulate critical settings. Organizations relying on ComfyUI-Manager for managing user interfaces in sensitive environments—such as government agencies, financial institutions, healthcare providers, and critical infrastructure operators—face heightened risks. The vulnerability could facilitate lateral movement within networks or enable attackers to establish persistent footholds. Given the remote exploitation capability without authentication, the threat surface is broad, potentially affecting any exposed ComfyUI-Manager instances. The absence of known exploits currently limits immediate impact, but the vulnerability's publication may prompt attackers to develop exploits, increasing future risk. European organizations must prioritize detection and remediation to prevent exploitation, especially those with public-facing management interfaces.

CWE-420Unprotected Alternate Channel (opens in a new tab)
Base weakness
The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
Architecture and Design
Identify all alternate channels and use the same protection mechanisms that are used for the primary channels.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Jan 2026, 16:23 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-420

Technical details

References

Community reviews

Related threats