CVE-2026-3306
Improper Authorization in GitHub Enterprise Server Allows Metadata Modification
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 | 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) |
| github | enterprise_server | to 3.14.24 (exc) |
| github | enterprise_server | From 3.15.0 (inc) to 3.15.19 (exc) |
| github | enterprise_server | From 3.16.0 (inc) to 3.16.15 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an improper authorization issue in GitHub Enterprise Server. It allows a user who has read access to a repository and write access to a project to modify issue and pull request metadata through the project. Specifically, when adding an item to a project that already exists, the system updates column values without verifying if the user has write permissions on the repository.
How can this vulnerability impact me? :
The vulnerability can allow users with limited permissions to modify metadata of issues and pull requests in repositories where they should not have write access. This could lead to unauthorized changes in project tracking and management data, potentially causing confusion, mismanagement, or manipulation of project workflows.
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, you should upgrade your GitHub Enterprise Server to one of the fixed versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6, or 3.19.3.