Quick answers
- Is CVE-2026-18382 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18382 being exploited in the wild.
- How severe is CVE-2026-18382?
- Medium severity, with a CVSS score of 6.8, published 30 July 2026.
- Which products and versions are affected?
- Red Hat Cost Management Metrics Operator unspecified.
- Is there a fix for CVE-2026-18382?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-18382 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-18382?
- Check whether you run Red Hat Cost Management Metrics Operator at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the koku-metrics-operator's CostManagementMetricsConfig custom resource (CR). The 'token_url' field in the CR lacks proper host validation, allowing a user with 'create' or 'update' permissions on the resource to specify an arbitrary URL. When the authentication type is set to 'service-account', the operator performs a POST request containing the tenant's Red Hat SSO client_id and client_secret to the user-supplied URL. This allows an attacker to intercept credentials that grant 'api.console' scope on console.redhat.com. Remediation involves enforcing a strict allow-list for the token endpoint (e.g., *.redhat.com) and requiring HTTPS.
Affected products
- Red Hat Cost Management Metrics Operator (koku-metrics-operator) unspecified
Timeline
- 2026-07-30: disclosed: Vulnerability reported and published to NVD