Summary
multicast in source builds from vulnerable setuptools dependency
Workarounds
- Further hardening in v2.0.9a4+ of the build process in CI builds allowing source builds to be verified via GH attestations.
References
- GHSA-5rjg-fvgr-3xxf
- pypa/setuptools#4946
Fixes
- https://github.com/reactive-firewall/multicast/blob/c5c7c7de272421d944beca8452871bca6bfd151f/tests/requirements.txt#L32
- https://github.com/reactive-firewall/multicast/blob/c5c7c7de272421d944beca8452871bca6bfd151f/docs/requirements.txt#L27
- https://github.com/reactive-firewall/multicast/blob/c5c7c7de272421d944beca8452871bca6bfd151f/requirements.txt#L26
- https://github.com/reactive-firewall/multicast/blob/c5c7c7de272421d944beca8452871bca6bfd151f/pyproject.toml#L2
Impact
- Some source-builds may be impacted by a CWE-1395 (eg. vulnerable
setuptoolsdependency).- Multicast prior to v2.0.9a3 on systems with minimal dependancies installed may use
setuptools <78.1.1and thus rely on a compromised dependency. In some cases there is a chance that source-builds would fail due to an exploit of the closely related CVE-2025-47273, or become arbitrarily modified.
- Multicast prior to v2.0.9a3 on systems with minimal dependancies installed may use
Affected versions
multicast (< 2.0.9a0)
Security releases
multicast → 2.0.9a0 (pip)
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Pre-release version v2.0.9a0 and later resolve the issue by bumping requirements to
setuptools>=80.4- Pre-release version v2.0.9a3 and later are recommended for improved stability over v2.0.9a0
Frequently Asked Questions
- What is GHSA-94V7-WXJ6-R2Q5? GHSA-94V7-WXJ6-R2Q5 is a medium-severity security vulnerability in multicast (pip), affecting versions < 2.0.9a0. It is fixed in 2.0.9a0.
- Which versions of multicast are affected by GHSA-94V7-WXJ6-R2Q5? multicast (pip) versions < 2.0.9a0 is affected.
- Is there a fix for GHSA-94V7-WXJ6-R2Q5? Yes. GHSA-94V7-WXJ6-R2Q5 is fixed in 2.0.9a0. Upgrade to this version or later.
- Is GHSA-94V7-WXJ6-R2Q5 exploitable, and should I be worried? Whether GHSA-94V7-WXJ6-R2Q5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-94V7-WXJ6-R2Q5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-94V7-WXJ6-R2Q5? Upgrade
multicastto 2.0.9a0 or later.