How severe is CVE-2026-46595?

CVE-2026-46595 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-46595?

CVE-2026-46595 affects the following packages: golang.org/x/crypto (Go). Ecosystems affected: Go.

How do I fix CVE-2026-46595?

Update golang.org/x/crypto to 0.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46595 is resolved across your whole dependency graph.

How do I detect CVE-2026-46595 in my Go dependencies?

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

How do I mitigate CVE-2026-46595 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-46595 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-46595 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 is the EPSS score for CVE-2026-46595?

CVE-2026-46595 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-46595?

CVE-2026-46595 is classified as CWE-863 (CWE-863), CWE-303 (CWE-303). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-46595 published, and has it been updated?

CVE-2026-46595 was published on May 22, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2026-46595 — x/crypto

CRITICAL

CVE-2026-46595 is a critical-severity (CVSS 10) CWE-863 vulnerability in golang.org/x/crypto. A fix is available for golang.org/x/crypto — see the affected versions and patch details below.

Invoking VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh

Also known asGHSA-x527-x647-q7ggGO-2026-5023

Published

May 22, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-46595.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-46595 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹golang.org/x/crypto

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

Description

Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/crypto`	all versions	0.52.0`go get golang.org/x/crypto@v0.52.0`

Affected Products

1 product · 1 configurations

Application

cryptogolang

< 0.52.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update golang.org/x/crypto to 0.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46595 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

golang.org/x/crypto/ssh is vulnerable to authorization bypass when SSH server configurations rely on source-address validation alongside non-public-key authentication callbacks. An attacker with low privileges who can authenticate through such a callback path may bypass intended source-address restrictions and gain…

Product	Fixed in	Advisory
Cryostat 4 on RHEL 9	`cryostat/cryostat-storage-rhel9:4.2.0-19`	RHSA-2026:48151
RHEM 1.0 for RHEL 9	`flightctl-0:1.0.3-1.el9em`	RHSA-2026:36796
RHEM 1.1 for RHEL 10	`flightctl-0:1.1.3-1.el10em`	RHSA-2026:41019
Cert Manager support for Red Hat OpenShift release 1.17	`cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791371080`	RHSA-2026:82304
Cert Manager support for Red Hat OpenShift release 1.17	`cert-manager/cert-manager-operator-rhel9:1791788287`	RHSA-2026:82322
Cert Manager support for Red Hat OpenShift release 1.19	`cert-manager/jetstack-cert-manager-rhel9:1786613805`	RHSA-2026:54531
Cluster Observability Operator 1.5.3	`cluster-observability-operator/cluster-observability-rhel9-operator:1787593637`	RHSA-2026:61314
DevWorkspace Operator 0.42	`devworkspace/devworkspace-rhel9-operator:1782401674`	RHSA-2026:36808

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-46595 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works