Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-27145 medium CVSS 6.5

Vulnerability in stdlib (CVE-2026-27145)

Summary

Vulnerability in stdlib (CVE-2026-27145). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.25.11, 1.26.4 or later.

Original description

The description as published by the source.

(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname.

With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates.

Source: GitHub Security Advisories (Global) 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-27145 has been found in stdlib.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade stdlib to 1.25.11, 1.26.4 or later.
If unsure, ask your IT team or search "stdlib CVE-2026-27145" on the vendor's site.

CVE-2026-27145 (stdlib) — CWE-606 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.25.11, 1.26.4 — 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

A vulnerability (CWE-606) exists in stdlib.

📍 Affected scope

Check the vendor advisory for the affected versions of stdlib.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.25.11, 1.26.4.

🛡️ 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 'stdlib' . 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 'stdlib' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade stdlib to 1.25.11, 1.26.4

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

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

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

Affected packages

Go stdlib
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.25.11"},{"introduced":"1.26.0-0"},{"fixed":"1.26.4"}]}]
Bitnami golang
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.25.11"},{"introduced":"1.26.0-0"},{"fixed":"1.26.4"}]}]

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