Red Hat Cost Management Metrics Operator CostManagementMetricsConfig authentication.type/token_endpoint input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $5k-$25k | 0.87+ |
Summary
A vulnerability was found in Red Hat Cost Management Metrics Operator and classified as problematic. This vulnerability affects unknown code of the component CostManagementMetricsConfig. Such manipulation of the argument authentication.type/token_endpoint leads to input validation. This vulnerability is traded as CVE-2026-18382. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Red Hat Cost Management Metrics Operator (the affected version is unknown). It has been rated as problematic. Affected by this issue is an unknown code of the component CostManagementMetricsConfig. The manipulation of the argument authentication.type/token_endpoint with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes:
A flaw was found in koku-metrics-operator. The operator's CostManagementMetricsConfig custom resource allows a user able to edit the CR to specify an arbitrary OAuth token endpoint. When authentication.type is set to service-account, the operator sends the tenant's Red Hat SSO client_id and client_secret to this user-controlled URL, allowing the attacker to obtain the credentials.
The advisory is available at access.redhat.com. This vulnerability is handled as CVE-2026-18382 since 07/30/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are needed for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 07/30/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51095). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/30/2026 Advisory disclosed07/30/2026 CVE reserved
07/30/2026 VulDB entry created
07/30/2026 VulDB entry last update
Sources
Vendor: redhat.comAdvisory: access.redhat.com
Status: Not defined
CVE: CVE-2026-18382 (🔒)
GCVE (CVE): GCVE-0-2026-18382
GCVE (VulDB): GCVE-100-384794
EUVD: 🔒
Entry
Created: 07/30/2026 14:26Updated: 07/30/2026 15:20
Changes: 07/30/2026 14:26 (52), 07/30/2026 15:20 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.