Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-18381 high CVSS 7.6

SSRF (Server-Side Request Forgery) in koku-metrics-operator for Red Hat OpenShift (CVE-2026-18381)

Summary

SSRF in koku-metrics-operator for Red Hat OpenShift (CVE-2026-18381). Confidential information can be exposed externally.

Original description

The description as published by the source.

A flaw was found in the koku-metrics-operator for Red Hat OpenShift. The operator's CostManagementMetricsConfig custom resource allows a user able to edit the CR to specify an arbitrary upload URL. The operator attaches its own Kubernetes service-account bearer token to queries sent to this user-controlled URL, allowing the attacker to obtain the token.

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-18381 has been found in koku-metrics-operator for Red Hat OpenShift.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "koku-metrics-operator for Red Hat OpenShift CVE-2026-18381" on the vendor's site.

CVE-2026-18381 (koku-metrics-operator for Red Hat OpenShift) — CWE-918 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
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 koku-metrics-operator for Red Hat OpenShift.

📍 Affected scope

Check the vendor advisory for the affected versions of koku-metrics-operator for Red Hat OpenShift.

🔥 Severity

Severity: High (CVSS 7.6/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・依存マニフェストで koku-metrics-operator for Red Hat OpenShift を使っているサービスとバージョンを洗い出す。

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

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

References

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