Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3

pypi-publish action revocation of CA in the chain that Sigstore uses in Trusted Publishing and Digital Attestations for PyPI

GHSA-5xjx-3w67-w9x9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pypa/gh-action-pypi-publish 1.14.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary The [pypi-publish action][pypi-publish] 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. [pypi-publish]: https://github.com/marketplace/actions/pypi-publish 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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-5xjx-3w67-w9x9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5xjx-3w67-w9x9

Advisory: pypi-publish action revocation of CA in the chain that Sigstore uses in Trusted Publishing and Digital Attestations for PyPI
IDs: GHSA-5xjx-3w67-w9x9
Record: https://patchnext.com/advisories/ghsa-5xjx-3w67-w9x9 (revision 1, source checked 30 Oct 2026, 21:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pypa/gh-action-pypi-publish 1.14.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions pypa/gh-action-pypi-publish: affected <= 1.14.2; fixed in 1.14.3

## Suggested inspection (read-only)
- GitHub Actions pypa/gh-action-pypi-publish: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pypa/gh-action-pypi-publish.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5xjx-3w67-w9x9 (GitHub-reviewed advisory GHSA-5xjx-3w67-w9x9 lists affected ranges: GitHub Actions pypa/gh-action-pypi-publish >=0 <=1.14.2)

Commands are suggestions: review each one before running it.

Loading voting…