EUVD-2026-45191
GHSA-qhvh-xjh2-7c8c
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network endpoint, low complexity; PR:L because write access to any repo is required; only metadata confidentiality impact, no integrity or availability effect.
Primary rating from Vendor (GitHub_P).
CVSS VectorVendor: GitHub_P
Lifecycle Timeline
1DescriptionCVE.org
A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with write access to any repository to read metadata from private repositories they did not have access to, including private repository owners and names, branch names, commit SHAs, commit messages, and the pushing actor. The delegated bypass endpoint resolved a rule suite directly from an attacker-supplied, encoded identifier without verifying that the requesting user could read the rule suite's repository, and because these identifiers are sequential an attacker could enumerate them across the instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3. This vulnerability was reported via the GitHub Bug Bounty program.
AnalysisAI
Missing authorization in GitHub Enterprise Server's delegated bypass endpoint exposes private repository metadata to any authenticated user with write access to a single repository on the same instance. The endpoint resolves rule suites from attacker-supplied encoded identifiers without verifying that the caller holds read permission on the target repository; because these identifiers are sequential, an attacker can enumerate them to harvest private repository names, owners, branch names, commit SHAs, commit messages, and pushing actors across the entire GHES instance. No public exploit identified at time of analysis; the issue was responsibly disclosed via the GitHub Bug Bounty program and vendor-released patches are available across all active support branches.
Technical ContextAI
GitHub Enterprise Server (CPE: cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*) implements repository rulesets with a 'delegated bypass' feature that allows certain actors to bypass push rules. The vulnerable endpoint in this feature accepts a user-supplied, encoded identifier representing a rule suite object, decodes it, and resolves the associated repository metadata - but omits the authorization check confirming the caller can read that repository. This is a textbook CWE-862 (Missing Authorization) / IDOR (Insecure Direct Object Reference) pattern: the object identifier is both externally controlled and sequential, enabling systematic traversal. The exposed data (repository names, owners, branch names, commit SHAs and messages, pushing actors) is normally protected by GitHub's repository-level access controls, which the bypass endpoint circumvents entirely.
RemediationAI
Upgrade GitHub Enterprise Server to the appropriate patched release for the deployed support branch: 3.17.18 (release notes: https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.18), 3.18.12 (https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.12), 3.19.9 (https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.9), 3.20.5 (https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.5), or 3.21.3 (https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.3). If immediate patching is not feasible, reduce the exploitable population by auditing and tightening repository write access grants - since any authenticated write-access holder can exploit the endpoint, revoking unnecessary write permissions directly limits exposure. There is no known configuration option to disable the delegated bypass endpoint specifically without disrupting ruleset functionality, so access restriction is the only meaningful compensating control pending patching.
Supply chain vulnerability in Eclipse Theia GitHub Actions workflow. The preview.yml workflow uses pull_request_target w
Supply chain attack vector in OpenLIT GitHub Actions workflows. The pull_request_target trigger with checkout enables ma
Eigent multi-agent workflow CI pipeline (ci.yml) uses pull_request_target with checkout of untrusted PR code, enabling a
An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. R
cmark-gfm is GitHub's extended version of the C reference implementation of CommonMark. Rated critical severity (CVSS 9.
An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowe
Unauthenticated infrastructure overwrite in Hoppscotch API development ecosystem before 2026.2.0. Attackers can overwrit
A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCrede
OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by
PolarLearn versions 0-PRERELEASE-15 and earlier lack proper state parameter validation in OAuth 2.0 authentication, enab
Path traversal in esm.sh CDN prior to version 0.0.0-20260116051925-c62ab83c589e allows unauthenticated remote attackers
actions/artifact is the GitHub ToolKit for developing GitHub Actions. Rated high severity (CVSS 7.5), this vulnerability
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today