Summary
pypi-publish action revocation of CA in the chain that Sigstore uses in Trusted Publishing and Digital Attestations for PyPI
The pypi-publish action versions before 1.14.2 used to bundle the emSign root CA trust store certificate through the certifi distribution. It has since been removed through the bundle and the new version no longer includes them.
Details
The certifi-provided TLS trust store is typically used by many projects in the Python ecosystem, including Sigstore that pypi-publish relies on for Trusted Publishing and Digital Attestations.
Related
The external compromise is being tracked at https://emudhra.we-have-a-problem.com
Impact
Affected versions
Security releases
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
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-5XJX-3W67-W9X9? GHSA-5XJX-3W67-W9X9 is a critical-severity security vulnerability in pypa/gh-action-pypi-publish (actions), affecting versions <= 1.14.2. It is fixed in 1.14.3.
- Which versions of pypa/gh-action-pypi-publish are affected by GHSA-5XJX-3W67-W9X9? pypa/gh-action-pypi-publish (actions) versions <= 1.14.2 is affected.
- Is there a fix for GHSA-5XJX-3W67-W9X9? Yes. GHSA-5XJX-3W67-W9X9 is fixed in 1.14.3. Upgrade to this version or later.
- Is GHSA-5XJX-3W67-W9X9 exploitable, and should I be worried? Whether GHSA-5XJX-3W67-W9X9 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-5XJX-3W67-W9X9 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-5XJX-3W67-W9X9? Upgrade
pypa/gh-action-pypi-publishto 1.14.3 or later.