VulnerabilityPublished 10 Jan 2026Updated 12 Jan 2026

CVE-2026-22777: Comfy-Org ComfyUI-Manager · CRLF Injection

Affects Comfy-Org ComfyUI-ManagerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.0.5 or 3.39.2 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.5, 3.39.2

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 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
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 26 Oct 2026.

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 or the CVSS exploit maturity 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 ComfyUI-Manager to 4.0.5 or 3.39.2; comfy-org/ComfyUI-Manager to 3.39.2.

Affected software

Product	Affected	Fixed in
Comfy-OrgComfyUI-Manager	Affected >=4.0.0 <4.0.5	Fixed in 4.0.5
Comfy-OrgComfyUI-Manager	Affected <3.39.2	Fixed in 3.39.2
GitHubcomfy-org/ComfyUI-Manager`pkg:github/comfy-org/ComfyUI-Manager`Other threats	Affected <3.39.2	Fixed in 3.39.2

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

AI-suggested

Immediately upgrade ComfyUI-Manager to versions 3.39.2 or 4.0.5 where the vulnerability is patched.
Implement strict input validation and sanitization on all HTTP query parameters to prevent injection of CRLF or other special characters.
Monitor the integrity of configuration files such as config.ini using file integrity monitoring tools to detect unauthorized changes promptly.
Restrict network access to the ComfyUI-Manager interface, limiting exposure to trusted networks or VPNs.
Employ web application firewalls (WAFs) with rules to detect and block CRLF injection attempts.
Conduct regular security audits and penetration testing focusing on injection vulnerabilities.
Educate developers and administrators about secure coding and configuration management practices to prevent similar issues.

Description

ComfyUI-Manager is an extension designed to enhance the usability of ComfyUI. Prior to versions 3.39.2 and 4.0.5, an attacker can inject special characters into HTTP query parameters to add arbitrary configuration values to the config.ini file. This can lead to security setting tampering or modification of application behavior. This issue has been patched in versions 3.39.2 and 4.0.5.

Impact

For European organizations, this vulnerability poses a significant risk to the integrity of applications relying on ComfyUI-Manager. Unauthorized modification of configuration files can lead to weakened security postures, enabling further attacks such as privilege escalation, bypassing security controls, or persistent backdoors. Organizations in sectors like finance, healthcare, and critical infrastructure that use ComfyUI-Manager for automation or UI management could face operational disruptions or data integrity issues. The remote, unauthenticated nature of the exploit increases the attack surface, especially for internet-facing deployments. Additionally, tampering with configuration files might evade detection if monitoring is insufficient, leading to prolonged compromise. The absence of known exploits currently provides a window for proactive mitigation, but the high CVSS score underscores the urgency of patching.

CWE-93Improper Neutralization of CRLF Sequences ('CRLF Injection') (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
Implementation
Avoid using CRLF as a special sequence.
Implementation
Appropriately filter or quote CRLF sequences in user-controlled input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Command Delimiters (opens in a new tab)
Web Server Logs Tampering (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 17 Jan 2026, 08:01 UTC

WeaknessesCWE-93

Technical details

References

Community reviews

Related threats