Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-42151 high CVSS 7.5

Information Disclosure in github.com/prometheus/prometheus (CVE-2026-42151)

Summary

vulnerability in github.com/prometheus/prometheus (CVE-2026-42151). Confidential information can be exposed externally. Exploitable via ``client_secret``. Mitigation: upgrade to `0.311.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-42151** has been found in github.com/prometheus/prometheus. Attackers can target a specific entry point like ``client_secret`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 7.5/10. What to do: upgrade github.com/prometheus/prometheus to **0.311.3** or later. If unsure, ask your IT team or search "github.com/prometheus/prometheus CVE-2026-42151" on the vendor's site.
CVE-2026-42151 (github.com/prometheus/prometheus) — CWE-200 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `client_secret` / `string` / `Secret` / `ClientSecret` Patched: `0.311.3` — apply immediately Workaround: Users who can not upgrade can switch to Managed Identity or Workload Identity authentication for Azure AD remote write, which do not involve a client secret. 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
**information disclosure** (CWE-200) exists in github.com/prometheus/prometheus. Attackers reach the vulnerable code path via ``client_secret`` without authentication.
📍 Affected scope
github.com/prometheus/prometheus — . Attack surface: `client_secret` / `string` / `Secret` / `ClientSecret`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.311.3**.
🛡️ Workaround
Workaround: Users who can not upgrade can switch to Managed Identity or Workload Identity authentication for Azure AD remote write, which do not involve a client secret.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/prometheus/prometheus' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/prometheus/prometheus' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate 
    Users who can not upgrade can switch to Managed Identity or Workload Identity authentication for Azure AD remote write, which do not involve a client secret.

    パッチが適用されるまでの応急処置として、Users who can not upgrade can switch to Managed Identity or Workload Identity authentication for Azure AD remote write, which do not involve a client secret. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade github.com/prometheus/prometheus to 0.311.3

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

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

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

Affected packages

Go github.com/prometheus/prometheus
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.311.3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →