Categories
CVE-2026-58612 high CVSS 7.4

SSRF (Server-Side Request Forgery) in Microsoft PowerShell Core (CVE-2026-58612)

Summary

SSRF in Microsoft PowerShell Core (CVE-2026-58612). Confidential information can be exposed externally.

Original description

The description as published by the source.

Server-side request forgery (ssrf) in Microsoft PowerShell Core allows an unauthorized attacker to disclose information over a network.

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-58612 has been found in Microsoft PowerShell Core.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Microsoft PowerShell Core CVE-2026-58612" on the vendor's site.

CVE-2026-58612 (Microsoft PowerShell Core) — CWE-918 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
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

SSRF (CWE-918) exists in Microsoft PowerShell Core.

📍 Affected scope

Check the vendor advisory for the affected versions of Microsoft PowerShell Core.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Microsoft PowerShell Core を使っているサービスとバージョンを洗い出す。

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

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

Affected packages

Bitnami powershell
[{"type":"SEMVER","events":[{"introduced":"7.6.0"},{"fixed":"7.6.5"},{"introduced":"7.4.0"},{"fixed":"7.4.19.0"},{"introduced":"7.5.0"},{"fixed":"7.5.10.0"}]}]

References

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