How severe is GHSA-6q48-6c7w-9gw2?

No CVSS score has been assigned to GHSA-6q48-6c7w-9gw2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6q48-6c7w-9gw2?

GHSA-6q48-6c7w-9gw2 affects the following packages: certifi (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6q48-6c7w-9gw2?

Update certifi to 2026.10.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q48-6c7w-9gw2 is resolved across your whole dependency graph.

How do I detect GHSA-6q48-6c7w-9gw2 in my PyPI dependencies?

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

How do I mitigate GHSA-6q48-6c7w-9gw2 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-6q48-6c7w-9gw2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6q48-6c7w-9gw2 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-6q48-6c7w-9gw2 published, and has it been updated?

GHSA-6q48-6c7w-9gw2 was published on October 20, 2026 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

certifi bundles emSign root CAs with compromised intermediate CA keysGHSA-6q48-6c7w-9gw2

GHSA-6q48-6c7w-9gw2 is a security vulnerability in certifi. A fix is available for certifi — see the affected versions and patch details below.

Also known asPYSEC-2026-4320

Published

Oct 20, 2026

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐍certifi

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

Description

Certifi versions before 2026.10.18 include the emSign ECC Root CA - G3 root certificate in their bundled CA store. Eight eMudhra intermediate CA certificates that chain to this root have compromised private keys and the CA has revoked them.

An attacker with one of the compromised keys can issue valid-looking certificates for any hostname. If the attacker is also on-path, they can intercept or modify TLS traffic from clients that trust the certifi bundle. Examples include requests, urllib3 and pip, and the Python.org macOS installer.

Certifi 2026.10.18 removed all emSign roots from the bundle. Certifi 2026.10.19 restored the emSign roots that are not affected. Upgrade to 2026.10.19 or later, and rebuild container images that vendor certifi.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`certifi`	≥ 2019.03.09&&< 2026.10.19	2026.10.19`pip install --upgrade 'certifi==2026.10.19'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for certifi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update certifi to 2026.10.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q48-6c7w-9gw2 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

Certifi versions before 2026.10.18 include the `emSign ECC Root CA - G3` root certificate in their bundled CA store. Eight eMudhra intermediate CA certificates that chain to this root have compromised private keys and the CA has revoked them. An attacker with one of the compromised keys can issue valid-looking certificates for any hostname. If the attacker is also on-path, they can intercept or modify TLS traffic from clients that trust the certifi bundle. Examples include `requests`, `urllib3` and `pip`, and the Python.org macOS installer. Certifi 2026.10.18 removed all emSign roots from t

O3 Security · Impact-Aware SCA

Is GHSA-6q48-6c7w-9gw2 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works