CVE-2026-3582
Incorrect Authorization in GitHub Enterprise Server Allows Data Exposure
Publication date: 2026-03-10
Last updated on: 2026-03-12
Assigner: GitHub, Inc. (Products Only)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| github | enterprise_server | to 3.16.15 (exc) |
| github | enterprise_server | From 3.17.0 (inc) to 3.17.12 (exc) |
| github | enterprise_server | From 3.18.0 (inc) to 3.18.6 (exc) |
| github | enterprise_server | From 3.19.0 (inc) to 3.19.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Incorrect Authorization issue in GitHub Enterprise Server. It allowed an authenticated user who had a classic personal access token (PAT) without the required 'repo' scope to access issues and commits from private and internal repositories using the search REST API endpoints.
However, to exploit this vulnerability, the user needed to already have access to the repository through organization membership or as a collaborator.
The vulnerability affected all versions of GitHub Enterprise Server before version 3.20 and was fixed in versions 3.16.15, 3.17.12, 3.18.6, and 3.19.3.
How can this vulnerability impact me? :
This vulnerability could allow an authenticated user with limited permissions (a PAT lacking the repo scope) to retrieve sensitive information such as issues and commits from private and internal repositories.
This could lead to unauthorized disclosure of potentially confidential or proprietary information within those repositories.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade your GitHub Enterprise Server to one of the fixed versions: 3.16.15, 3.17.12, 3.18.6, or 3.19.3.
Ensure that personal access tokens (PATs) without the repo scope are not used to access private or internal repositories.