How severe is GHSA-p423-j2cm-9vmq?

No CVSS score has been assigned to GHSA-p423-j2cm-9vmq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p423-j2cm-9vmq?

GHSA-p423-j2cm-9vmq affects the following packages: cryptography (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-p423-j2cm-9vmq?

Update cryptography to 46.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p423-j2cm-9vmq is resolved across your whole dependency graph.

How do I detect GHSA-p423-j2cm-9vmq in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cryptography. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p423-j2cm-9vmq 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.

How does O3 Security protect against GHSA-p423-j2cm-9vmq?

O3 pinpoints whether GHSA-p423-j2cm-9vmq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p423-j2cm-9vmq actively exploited in the wild?

No public exploit code has been indexed for GHSA-p423-j2cm-9vmq 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.

What type of vulnerability is GHSA-p423-j2cm-9vmq?

GHSA-p423-j2cm-9vmq is classified as Buffer Overflow (CWE-119), CWE-131 (CWE-131). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-p423-j2cm-9vmq published, and has it been updated?

GHSA-p423-j2cm-9vmq was published on April 8, 2026 and was last updated on June 5, 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

GHSA-p423-j2cm-9vmq

GHSA-p423-j2cm-9vmq is a Buffer Overflow vulnerability in cryptography. O3 Security confirms whether GHSA-p423-j2cm-9vmq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs

Also known asCVE-2026-39892PYSEC-2026-36

Published

Apr 8, 2026

Updated

Jun 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍cryptography

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

If a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. For example:

h = Hash(SHA256())
b.update(buf[::-1])

would read past the end of the buffer on Python >3.11

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cryptography`	≥ 45.0.0&&< 46.0.7	46.0.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cryptography. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update cryptography to 46.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p423-j2cm-9vmq 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.
How O3 protects you
O3 pinpoints whether GHSA-p423-j2cm-9vmq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p423-j2cm-9vmq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. `Hash.update()`), this could lead to buffer overflows. For example: ```python h = Hash(SHA256()) b.update(buf[::-1]) ``` would read past the end of the buffer on Python >3.11

O3 Security · Impact-Aware SCA

Is GHSA-p423-j2cm-9vmq in your dependencies?

O3 detects GHSA-p423-j2cm-9vmq across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works