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

Vulnerability in golang.org/x/net (CVE-2026-25680)

Summary

Vulnerability in golang.org/x/net (CVE-2026-25680). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.55.0 or later.

Original description

The description as published by the source.

Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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 weakness called CVE-2026-25680 was discovered in golang.org/x/net.
Severity is Medium (CVSS 6.5/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "golang.org/x/net CVE-2026-25680".

CVE-2026-25680 (golang.org/x/net). Severity: Medium / CVSSv3 6.5. Category: CWE-400.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-25680) in golang.org/x/net. A serious software flaw has been identified.

📍 Affected scope

Target versions of golang.org/x/net (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Exploitation requires specific conditions but can cause real harm if successful.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-400)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

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/net' . | grep -v node_modules

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

  2. 6
    Apply patch patch 
    Upgrade golang.org/x/net to 0.55.0

    ステージング環境で 0.55.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

Go golang.org/x/net
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.55.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