How severe is CVE-2026-22777?

CVE-2026-22777 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-22777?

CVE-2026-22777 affects the following packages: comfy-cli (PyPI), comfy-cli (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-22777?

Update comfy-cli to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22777 is resolved across your whole dependency graph.

How do I detect CVE-2026-22777 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for comfy-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-22777 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-22777 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-22777 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-22777?

CVE-2026-22777 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-22777?

CVE-2026-22777 is classified as CWE-93 (CWE-93). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-22777?

A Nuclei detection template exists for CVE-2026-22777, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-22777 published, and has it been updated?

CVE-2026-22777 was published on January 10, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2026-22777 — comfy-cli

HIGHFix: Comfy-Org/ComfyUI-Manager@f4fa394

CVE-2026-22777 is a high-severity (CVSS 7.5) CWE-93 vulnerability in comfy-cli. A fix is available for comfy-cli — see the affected versions and patch details below.

ComfyUI-Manager is Vulnerable to CRLF Injection in Configuration Handler

Also known asGHSA-562r-8445-54r2PYSEC-2026-1260

Published

Jan 10, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22777.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍comfy-cli🐍comfy-cli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Vulnerability Type: CRLF Injection via ConfigParser

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.

Affected Users: Users running ComfyUI-Manager in environments where ComfyUI is configured with the --listen option to allow remote access.

CVSS Score: 7.5 (High)

Patches

Fixed in the following versions:

3.39.2 (v3.x branch)
4.0.5 (v4.x branch)

Sanitization logic was added to the write_config() function to remove CRLF and NULL characters from all string values.

Workarounds

If upgrading is not possible:

Run ComfyUI-Manager only on trusted networks
Block external access via firewall
Run on localhost only without the --listen option

References

Credit

This vulnerability was reported by:

李存义 [email protected]
D0n9 Li [email protected]
Swings [email protected]
Osword from SGLAB of Legendsec at Qi'anxin Group [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`comfy-cli`	≥ 4.0.0&&< 4.0.5	4.0.5`pip install --upgrade 'comfy-cli==4.0.5'`
🐍PyPI	`comfy-cli`	all versions	3.39.2`pip install --upgrade 'comfy-cli==3.39.2'`

Affected Products

1 product · 2 configurations

Application

comfyui-managercomfy

≥ 4.0.3 && < 4.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for comfy-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update comfy-cli to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22777 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2026-22777

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-22777 -u https://target

Template: ComfyUI-Manager < 3.39.2 - CRLF Configuration Injection
Severity: high
Impact: Attackers can modify application configuration, potentially altering security settings or application behavior.
Remediation: This issue has been patched in versions 3.39.2 and 4.0.5.

Template by ProjectDiscovery nuclei-templates (TassioSales, DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

## Impact **Vulnerability Type**: CRLF Injection via ConfigParser 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. **Affected Users**: Users running ComfyUI-Manager in environments where ComfyUI is configured with the `--listen` option to allow remote access. **CVSS Score**: 7.5 (High) ## Patches Fixed in the following versions: - **3.39.2** (v3.x branch) - **4.0.5** (v4.x branch) Sanitization logic was added to the `wri