Improper authorization in GitHub Projects allows modification of issue and pull request metadata without repository write access
Noroxi assessment
Priority: Monitor (action score 21/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: GitHub Enterprise Server 3.14.24, 3.15.19, 3.16.15.
Low priority for now. Upgrade to GitHub Enterprise Server 3.14.24, 3.15.19, 3.16.15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 10, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-639
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_P
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| github | enterprise server | cpe:2.3:a:github:enterprise_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- github enterprise serverbefore 3.14.24
- github enterprise server3.15.0 and later · before 3.15.19
- github enterprise server3.16.0 and later · before 3.16.15
- github enterprise server3.17.0 and later · before 3.17.12
- github enterprise server3.18.0 and later · before 3.18.6
- github enterprise server3.19.0 and later · before 3.19.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.
GitHub Enterprise Server
- 3.14.0 and later · up to and including 3.14.23affected · semverfixed in 3.14.24
- 3.15.0 and later · up to and including 3.15.18affected · semverfixed in 3.15.19
- 3.16.0 and later · up to and including 3.16.14affected · semverfixed in 3.16.15
- 3.17.0 and later · up to and including 3.17.11affected · semverfixed in 3.17.12
- 3.18.0 and later · up to and including 3.18.5affected · semverfixed in 3.18.6
- 3.19.0 and later · up to and including 3.19.2affected · semverfixed in 3.19.3
Same product
github: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection61This week
- CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server55Plan
- CVE-2024-9487An Improper Verification of Cryptographic Signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed46Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-1355Feb 18, 2026 · Missing Authorization Check in GitHub Enterprise Server Allows Unauthorized Uploads to Repository Migration Exports24Monitor
- ← EarlierCVE-2026-1999Feb 18, 2026 · Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized merging of pull requests28Monitor
- Later →CVE-2026-3854Mar 10, 2026 · Remote code execution via git push option injection in GitHub Enterprise Server34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitHub Enterprise Server | 3.14.24 | Vendor (CNA) |
| GitHub Enterprise Server | 3.15.19 | Vendor (CNA) |
| GitHub Enterprise Server | 3.16.15 | Vendor (CNA) |
| GitHub Enterprise Server | 3.17.12 | Vendor (CNA) |
| GitHub Enterprise Server | 3.18.6 | Vendor (CNA) |
| GitHub Enterprise Server | 3.19.3 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-27 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+138 d
- TodayOct 20, 2026+224 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- ahacker1finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-584542 days apartImproper authorization fallback allows scoped user-to-server token installation escape in GitHub Enterprise Server28Monitor
- CVE-2025-8447197 days apartIncorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed read-only access28Monitor
- CVE-2026-75101196 days apartAuthorization bypass vulnerability in GitHub Enterprise Server allowed reading of private pull request diffs and patches via repository name collision24Monitor
- CVE-2026-330742 days apartAuthorization bypass in GitHub Enterprise Server secret scanning push protection allows cross-repository modification of delegated bypass reviewers21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
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/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
nvd-secondary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);res.json(invoice);Fixed
const invoice = await Invoice.findOne({ id: req.params.id, ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- docs.github.com/en/enterprise-server@3.15/admin/release-notes#3.15.19
- docs.github.com/en/enterprise-server@3.16/admin/release-notes#3.16.15
- docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.12
- docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.6
- docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.