Service-account token theft via unvalidated Prometheus address
Published Jul 30, 2026 · Updated Jul 30, 2026
SSRF in Red Hat Cost Management Metrics Operator 4 allows remote authenticated users to steal its service-account token through a crafted CR. The spec.prometheus_config.service_address field accepts any host, and the Prometheus collector sends queries there with its mounted bearer token. Create or update access to CostManagementMetricsConfig in the operator namespace is required; the token reads named Secrets cluster-wide.
Summary
What happened
SSRF in Red Hat Cost Management Metrics Operator 4 allows remote authenticated users to steal its service-account token through a crafted CR. The spec.prometheus_config.service_address field accepts any host, and the Prometheus collector sends queries there with its mounted bearer token. Create or update access to CostManagementMetricsConfig in the operator namespace is required; the token reads named Secrets cluster-wide.
The record
- CVE
- CVE-2026-18381
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- 389 Directory Server
- Product
- Cost Management Metrics Operator 4
- Classifications
- CWE-918, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo