cve.bz

CVE-2026-3306 github enterprise server

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in github enterprise server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
An improper authorization vulnerability was identified in GitHub Enterprise Server that allowed a user with read access to a repository and write access to a project to modify issue and pull request metadata through the project. When adding an item to a project that already existed, column value updates were applied without verifying the actor's repository write permissions. This vulnerability was reported via the GitHub Bug Bounty program and has been fixed in GitHub Enterprise Server versions 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6 and 3.19.3.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-03-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.14.24
  • GitHub Enterprise Server: fixed in 3.15.19
  • GitHub Enterprise Server: fixed in 3.16.15
  • GitHub Enterprise Server: fixed in 3.17.12
  • GitHub Enterprise Server: fixed in 3.18.6
  • GitHub Enterprise Server: fixed in 3.19.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-3306 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-3306?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-3306?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-3306 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.14.0 through 3.14.23
GitHub Enterprise Serverfrom 3.15.0 through 3.15.18
GitHub Enterprise Serverfrom 3.16.0 through 3.16.14
GitHub Enterprise Serverfrom 3.17.0 through 3.17.11
GitHub Enterprise Serverfrom 3.18.0 through 3.18.5
GitHub Enterprise Serverfrom 3.19.0 through 3.19.2

Fixed in

ProductFixed in
GitHub Enterprise Server3.14.24
GitHub Enterprise Server3.15.19
GitHub Enterprise Server3.16.15
GitHub Enterprise Server3.17.12
GitHub Enterprise Server3.18.6
GitHub Enterprise Server3.19.3

References

Check your stackJSON