Skip to content
Fencer Intel
critical —

GHSA-5xjx-3w67-w9x9 json

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

published 15d ago modified 15d ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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

Patch / fix

  • github-actions pypa/gh-action-pypi-publish 1.14.3

Is GHSA-5xjx-3w67-w9x9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
github-actions pypa/gh-action-pypi-publish
<1.14.3
1.14.3

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.