How severe is GHSA-95pq-hr8p-f5g7?

GHSA-95pq-hr8p-f5g7 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-95pq-hr8p-f5g7?

GHSA-95pq-hr8p-f5g7 affects the following packages: comfyui-manager (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-95pq-hr8p-f5g7?

Update comfyui-manager to 3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95pq-hr8p-f5g7 is resolved across your whole dependency graph.

How do I detect GHSA-95pq-hr8p-f5g7 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for comfyui-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-95pq-hr8p-f5g7 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.

How does O3 Security protect against GHSA-95pq-hr8p-f5g7?

O3 pinpoints whether GHSA-95pq-hr8p-f5g7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-95pq-hr8p-f5g7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-95pq-hr8p-f5g7 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 type of vulnerability is GHSA-95pq-hr8p-f5g7?

GHSA-95pq-hr8p-f5g7 is classified as CWE-420 (CWE-420). 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 GHSA-95pq-hr8p-f5g7?

A Nuclei detection template exists for GHSA-95pq-hr8p-f5g7, 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 GHSA-95pq-hr8p-f5g7 published, and has it been updated?

GHSA-95pq-hr8p-f5g7 was published on June 22, 2026 and was last updated on July 13, 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

GHSA-95pq-hr8p-f5g7

HIGH

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

Also known asCVE-2025-67303PYSEC-2026-2422

Published

Jun 22, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍comfyui-manager

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

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

Path Migration: Configuration files moved from unprotected user/default/ComfyUI-Manager/ to protected user/__manager/
Protected Directory: The new __manager/ directory leverages ComfyUI's System User Protection API, which blocks external web API access
Security Level Enforcement: Settings below "normal" are automatically raised to "normal" during migration
Legacy Backup: Old data is backed up to .legacy-manager-backup/ with startup reminders until manually deleted
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 ComfyUI/#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

Credit

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`comfyui-manager`	all versions	3.38

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for comfyui-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update comfyui-manager to 3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95pq-hr8p-f5g7 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 O3 protects you
O3 pinpoints whether GHSA-95pq-hr8p-f5g7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-95pq-hr8p-f5g7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 s

O3 Security · Impact-Aware SCA

Is GHSA-95pq-hr8p-f5g7 in your dependencies?

O3 detects GHSA-95pq-hr8p-f5g7 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-95pq-hr8p-f5g7

Blast Radius

Description

Impact

Vulnerability Details

Potential Attack Scenarios

Affected Configurations

Patches

Requirements

What the Patch Does

Patch Details

Workarounds

Resources

Credit

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-95pq-hr8p-f5g7 in your dependencies?