Medium [CVE-2026-72924] Forwarded services exposed on all network interfaces by default
This medium-severity Red Hat Linux advisory covers CVE-2026-72924 affecting Red Hat OpenShift GitOps, Red Hat OpenStack Platform 18.0.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
GitHub CLI (gh) is GitHub's official command line tool. Versions 2.28.0 through 2.97.0 bind the local listener created by gh codespace ports forward to all available network interfaces by default.
While port forwarding is active, a service in a Codespace can therefore become reachable through the user's non-loopback local IP addresses by other hosts that can route to the user's machine. This behavior does not change the GitHub-side visibility of the Codespaces port.
Instead, it exposes the forwarded service through a wildcard-bound listener on the user's local machine, even when the source Codespaces port remains private. Exploitation requires a network-adjacent attacker to reach the victim's machine while forwarding is active.
This issue is fixed in version 2.98.0. This can lead to unauthorized access to internal services.
In standard Red Hat deployments, the GitHub CLI tool is used interactively rather than as a persistent background daemon, limiting exposure to active developer sessions. When forwarding is executed, the tool binds to all local network adapters instead of strictly to loopback interfaces, exposing remote services to adjacent network hosts.
Systems not utilizing the Codespaces port redirection feature or protected by host firewalls do not expose services to outside hosts. Red Hat severity: Moderate — CVSS 4.6 (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).
- 2.28.0
- 2.97.0
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation checklist
- There are no known mitigations available for this vulnerability at this time. Red Hat recommends applying the available security update once it is released.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.