How severe is CVE-2026-39828?

CVE-2026-39828 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-39828?

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

How do I fix CVE-2026-39828?

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-39828 is resolved across your whole dependency graph.

How do I detect CVE-2026-39828 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-39828 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 CVE-2026-39828 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-39828 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-39828?

CVE-2026-39828 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-39828?

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

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

CVE-2026-39828 was published on May 22, 2026 and was last updated on September 25, 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

MEDIUM severity

CVE-2026-39828 — x/crypto

MEDIUM

CVE-2026-39828 is a medium-severity (CVSS 6.3) CWE-295 vulnerability in golang.org/x/crypto. A fix is available for golang.org/x/crypto — see the affected versions and patch details below.

Invoking bypass of certificate restrictions in golang.org/x/crypto/ssh

Also known asGHSA-45gg-vh54-h5m9GO-2026-5014

Published

May 22, 2026

Updated

Sep 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-39828.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

Of 389,824 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

When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.

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-39828 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.

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

This is an Important security flaw in the `golang.org/x/crypto/ssh` library. When an SSH server utilizing this library is configured with specific authentication callbacks that return a `PartialSuccessError` with non-nil permissions, an attacker could bypass intended certificate restrictions, such as `force-command`.…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-39828 (CC BY 4.0)

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-acmesolver-rhel9:1786613805`	RHSA-2026:54531
DevWorkspace Operator 0.42	`devworkspace/devworkspace-project-clone-rhel9:1782400868`	RHSA-2026:36808
Logging Subsystem for Red Hat OpenShift 6.6	`openshift-logging/cluster-logging-rhel9-operator:1788439505`	RHSA-2026:66521

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-39828 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works