Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-67303 — comfyui-manager

🟠 CVSS 8.0 — High ⚠️ Exploit Public CWE-420 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

ComfyUI-Manager has an Unprotected Alternate Channel (CWE-420)

Impact

An Unprotected Alternate Channel (CWE-420) vulnerability was discovered in ComfyUI-Manager versions prior to 3.38.

Vulnerability Details

In affected versions, ComfyUI-Manager stored its configuration in the user/default/ComfyUI-Manager/ directory, which was accessible via ComfyUI's web APIs without proper access control. This unprotected alternate channel allowed remote attackers to read and manipulate configuration files and critical data through the web interface.

Potential Attack Scenarios

An attacker exploiting this vulnerability could:

  • Modify security settings: Lower the security level from "strong" to "weak" to enable more dangerous operations
  • Tamper with custom node sources: Add malicious custom node repositories
  • Manipulate snapshot data: Corrupt or alter system snapshots
  • Change manager behavior: Alter various manager configuration settings

Affected Configurations

| Configuration | Risk Level |

|---------------|------------|

| Systems running with --listen 0.0.0.0 (externally exposed) | HIGH |

| Systems behind reverse proxy without proper access control | MEDIUM |

| Local-only installations (default, localhost only) | NOT AFFECTED |

Patches

This issue has been patched in ComfyUI-Manager version 3.38.

Requirements

| Component | Minimum Version | Notes |

|-----------|-----------------|-------|

| ComfyUI | v0.3.76+ | Required for System User Protection API |

| ComfyUI-Manager | v3.38+ | Contains the security fix |

What the Patch Does

1. Path Migration: Configuration files moved from unprotected user/default/ComfyUI-Manager/ to protected user/__manager/

2. Protected Directory: The new __manager/ directory leverages ComfyUI's System User Protection API, which blocks external web API access

3. Security Level Enforcement: Settings below "normal" are automatically raised to "normal" during migration

4. Legacy Backup: Old data is backed up to .legacy-manager-backup/ with startup reminders until manually deleted

5. Fallback Protection: If ComfyUI < v0.3.76, Manager forces "strong" security mode, blocking new installations until ComfyUI is updated

Patch Details

  • Commit: aaed1dc
  • Pull Request: [ComfyUI-Manager/#2338](https://github.com/Comfy-Org/ComfyUI-Manager/pull/2338) [ComfyUI/#10966](https://github.com/Comfy-Org/ComfyUI/pull/10966)
  • Changes: +780 lines, −61 lines across 13 files

Workarounds

If immediate upgrade is not possible, apply the following mitigations:

| Mitigation | Effectiveness | Effort |

|------------|---------------|--------|

| Remove --listen 0.0.0.0 flag (use localhost only) | HIGH | Low |

| Implement firewall rules to block external access to ComfyUI ports | HIGH | Medium |

| Use reverse proxy with authentication (e.g., nginx + basic auth) | HIGH | Medium |

| Restrict network access to trusted IPs only | MEDIUM | Low |

Note: These are temporary mitigations. Upgrading to v3.38+ is strongly recommended.

Resources

  • [NVD - CVE-2025-67303](https://nvd.nist.gov/vuln/detail/CVE-2025-67303)
  • [ComfyUI-Manager v3.38 Security Migration Guide](https://github.com/Comfy-Org/ComfyUI-Manager/blob/main/docs/en/v3.38-userdata-security-migration.md)
  • [Patch Pull Request ComfyUI-Manager/#2338](https://github.com/Comfy-Org/ComfyUI-Manager/pull/2338)
  • [Patch Pull Request ComfyUI/#10966](https://github.com/Comfy-Org/ComfyUI/pull/10966)

Credit

This vulnerability was reported by Ricter Zheng (ricterzheng / 郑杜涛) from Tencent Xuanwu Lab <[email protected]>

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: None.

Weakness class

CVE-2025-67303 is classified as CWE-420: Unprotected Alternate Channel. The product protects a primary channel, but it does not use the same level of protection for an alternate channel.

Affected software

CVE-2025-67303 is recorded against 1 package.

  • comfyui-manager (fixed in 3.38)

Timeline and source

Published on 22 June 2026 and last revised on 13 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

comfyui-manager has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-420: Unprotected Alternate Channel) in other software:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CWE CWE-420
Public Exploit ⚠️ Yes
Source OSV
Published 2026-06-22
Updated 2026-08-20
Modified 2026-07-13

Affected Packages

Software From version Fixed in
comfyui-manager — 3.38

Similar Threats

Exploit Protection

Are you running comfyui-manager?

CVE-2025-67303 carries CVSS 8.0 High rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2025-67303 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓