CVE-2024-21576
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedComfyUI-Bmad-Nodes is vulnerable to Code Injection. The issue stems from a validation bypass in the BuildColorRangeHSVAdvanced, FilterContour and FindContour custom nodes. In the entrypoint function to each node, there’s a call to eval which can be triggered by generating a workflow that injects a crafted string into the node. This can result in executing arbitrary code on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCode injection vulnerability in ComfyUI-Bmad-Nodes affecting BuildColorRangeHSVAdvanced, FilterContour, and FindContour nodes. These nodes use eval() without proper input validation, allowing attackers to inject arbitrary Python code via crafted workflow JSON.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ComfyUI-Bmad-Nodes extension is installedCheck for the presence of the ComfyUI-Bmad-Nodes extension directory (typically under ComfyUI/custom_nodes/) and list its filesAffected if The extension directory exists and contains the affected nodes module
-
Identify the installed version of ComfyUI-Bmad-NodesLocate and read the version file (usually version.py, __init__.py, or pyproject.toml) within the extension directory to determine the version numberAffected if Version cannot be determined or is within any unpatched version range
-
Check if affected nodes are loadedInspect the Python files for BuildColorRangeHSVAdvanced, FilterContour, and FindContour nodes in the extension (look for node class definitions)Affected if Any of these three node classes exist in the extension files
-
Inspect node implementation for eval() usageOpen the Python source files containing the affected nodes and search for eval() function calls without proper sanitizationAffected if eval() is used in the node code without input validation safeguards
-
Review loaded workflows for affected nodesExamine any saved workflow JSON files (.json) in the ComfyUI workflow directory or within the custom_nodes data folders for references to BuildColorRangeHSVAdvanced, FilterContour, or FindContourAffected if Workflows reference or use any of the three vulnerable nodes
A user is affected if ComfyUI-Bmad-Nodes is installed with any of the three vulnerable nodes present and those nodes process untrusted workflow JSON input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or disable the affected nodes until a patched version is available. If immediate remediation is needed, audit workflows for usage of these nodes and consider network isolation of the ComfyUI instance.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21576 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data