How severe is GHSA-5xjx-3w67-w9x9?

No CVSS score has been assigned to GHSA-5xjx-3w67-w9x9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5xjx-3w67-w9x9?

GHSA-5xjx-3w67-w9x9 affects the following packages: pypa/gh-action-pypi-publish (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-5xjx-3w67-w9x9?

Update pypa/gh-action-pypi-publish to 1.14.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xjx-3w67-w9x9 is resolved across your whole dependency graph.

How do I detect GHSA-5xjx-3w67-w9x9 in my GitHub Actions dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypa/gh-action-pypi-publish, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5xjx-3w67-w9x9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5xjx-3w67-w9x9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5xjx-3w67-w9x9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5xjx-3w67-w9x9 published, and has it been updated?

GHSA-5xjx-3w67-w9x9 was published on October 30, 2026 and was last updated on October 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 GitHub Actions

Not in CISA KEV

pypi-publish action revocation of CA in the chain that Sigstore uses in Trusted Publishing and Digital Attestations for PyPIGHSA-5xjx-3w67-w9x9

GHSA-5xjx-3w67-w9x9 is a security vulnerability in pypa/gh-action-pypi-publish. A fix is available for pypa/gh-action-pypi-publish — see the affected versions and patch details below.

Published

Oct 30, 2026

Updated

Oct 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦pypa/gh-action-pypi-publish

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

The external compromise is being tracked at https://emudhra.we-have-a-problem.com

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`pypa/gh-action-pypi-publish`	all versions	1.14.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypa/gh-action-pypi-publish, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pypa/gh-action-pypi-publish to 1.14.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xjx-3w67-w9x9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-5xjx-3w67-w9x9 in your dependencies?

Find it across GitHub Actions, including transitive dependencies.

Scan my dependencies How O3 SCA works