Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_P

CVE-2026-14340: An incorrect authorization vulnerability in GitHub Enterprise Server allows issue creation in unrelated public repositories

MediumCVSS 5.3 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.42% (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.
  • Fixed version: GitHub Enterprise Server 3.16.20, 3.17.17, 3.18.11.

Low priority for now. Upgrade to GitHub Enterprise Server 3.16.20, 3.17.17, 3.18.11 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 incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a user-to-server token scoped to a GitHub App installation to perform certain write operations on public repositories outside the token's intended scope. This was possible because the authorization check only verified that the installation had read permissions on the target repository rather than verifying that the token's installation was explicitly granted access to that repository. An attacker who obtained a victim's user-to-server token could create issues, issue comments, commit comments, and private vulnerability reports on any public repository, appearing as the victim user with no indication of the app involvement. This vulnerability was fixed by adding a repository scope check for user-to-server tokens issued by global apps. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.

Published
Jul 1, 2026
Updated
Oct 25, 2026
EPSS
0.4% · 37th percentile

Report tools

JSON

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
no
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
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-14340

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for github records
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
githubenterprise server

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.16.0 and later · up to and including 3.16.19affected · semverfixed in 3.16.20
    • 3.17.0 and later · up to and including 3.17.16affected · semverfixed in 3.17.17
    • 3.18.0 and later · up to and including 3.18.10affected · semverfixed in 3.18.11
    • 3.19.0 and later · up to and including 3.19.7affected · semverfixed in 3.19.8
    • 3.20.0 and later · up to and including 3.20.3affected · semverfixed in 3.20.4
    • 3.21.0 and later · up to and including 3.21.1affected · semverfixed in 3.21.2
Affected versions · NVD (6)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • github enterprise serverbefore 3.16.20
  • github enterprise server3.17.0 and later · before 3.17.17
  • github enterprise server3.18.0 and later · before 3.18.11
  • github enterprise server3.19.0 and later · before 3.19.8
  • github enterprise server3.20.0 and later · before 3.20.4
  • github enterprise server3.21.0 and later · before 3.21.2

Same product

github: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
    61This week
  • CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
    55Plan
  • CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
    47Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-9132Jun 30, 2026 · Missing authorization vulnerability in GitHub Enterprise Server allowed disclosure of private repository contents via the Copilot pull request diff summary…
    24Monitor
  • ← EarlierCVE-2026-10585Jun 30, 2026 · Stored cross-site scripting vulnerability in GitHub Enterprise Server allowed arbitrary JavaScript execution via crafted Discussion titles in the Q&A category
    25Monitor
  • Later →CVE-2026-15007Jul 17, 2026 · Denial of service vulnerability in GitHub Enterprise Server allowed service disruption via deeply nested YAML in release notes…
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
GitHub Enterprise Server3.16.20Vendor (CNA)
GitHub Enterprise Server3.17.17Vendor (CNA)
GitHub Enterprise Server3.18.11Vendor (CNA)
GitHub Enterprise Server3.19.8Vendor (CNA)
GitHub Enterprise Server3.20.4Vendor (CNA)
GitHub Enterprise Server3.21.2Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-1999133 days apartIncorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized merging of pull requests
    28Monitor
  • CVE-2025-6981351 days apartIncorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized read-only access
    21Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link.

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-863 · Incorrect Authorization

CVSS 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

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.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records