Multicluster Global Hub: Active Debug Code
CVE-2026-83550 is a high-severity active debug code vulnerability in Multicluster Global Hub from Red Hat, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Multicluster Global Hub you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Multicluster Global Hub | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in postgres-exporter. Due to the blank import of `net/http/pprof`, debug endpoints are exposed on the unauthenticated metrics listener. A remote attacker within the cluster network can access these endpoints. This allows for information disclosure, potentially revealing process arguments, full goroutine stacks, and sensitive data like database connection strings or passwords from heap dumps. Additionally, repeated CPU profiling through these endpoints can lead to a denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Active Debug Code
The product is released with debugging code still enabled or active.
How developers prevent this class of flaw
- Remove debug code before deploying the application.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Multicluster Global Hub
- 7.2 High severity
- 7.5 High severity
- 7.3 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
Recent Active Debug Code vulnerabilities
- 9.5 Critical severity
- 8.9 High severity
- 9.1 Critical severity
- 8.2 High severity
- 9.0 Critical severity
- 7.5 High severity
Spotted an error? Tell us.