Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46595 critical CVSS 10.0

Authorization Flaw in golang.org/x/crypto (CVE-2026-46595)

Summary

Vulnerability in golang.org/x/crypto (CVE-2026-46595). Confidential information can be exposed externally. Mitigation: upgrade to 0.52.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-46595 has been found in golang.org/x/crypto.
Confidential information can be exposed externally. CVSS score: 10.0/10.
What to do: upgrade golang.org/x/crypto to 0.52.0 or later.
If unsure, ask your IT team or search "golang.org/x/crypto CVE-2026-46595" on the vendor's site.

CVE-2026-46595 (golang.org/x/crypto) — CWE-863 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.52.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in golang.org/x/crypto.

📍 Affected scope

Check the vendor advisory for the affected versions of golang.org/x/crypto.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.52.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang.org/x/crypto' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'golang.org/x/crypto' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で golang.org/x/crypto を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade golang.org/x/crypto to 0.52.0

    ステージング環境で 0.52.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go golang.org/x/crypto
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.52.0"}]}]
go golang.org/x/crypto/ssh
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.52.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details