Enterprise ServerApplication · GitHub
CVE-2026-8106
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA reflected HTML injection vulnerability was identified in the GitHub Enterprise Server Management Console login page that could allow credential theft. The redirect_to query parameter on the /setup/unlock endpoint was reflected into an HTML attribute without proper sanitization, enabling an attacker to inject a form element that could capture administrator credentials. Exploitation required an administrator to click a crafted link and enter their credentials. This vulnerability affected GitHub Enterprise Server versions 3.19.1 through 3.19.5 and 3.20.0 through 3.20.1, and was fixed in versions 3.19.6 and 3.20.2. This vulnerability was reported via the GitHub Bug Bounty program.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReflected HTML injection in GitHub Enterprise Server Management Console login page. The redirect_to query parameter on /setup/unlock endpoint is reflected into an HTML attribute without sanitization, allowing injection of malicious form elements to capture administrator credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise ServerApplication
>= 3.19.1, < 3.19.6>= 3.20.0, < 3.20.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check GitHub Enterprise Server versionAccess the Management Console and navigate to the Site Admin settings, or run 'ghe-version' from the command line if you have SSH access to the applianceAffected if The installed version falls within 3.19.1 to 3.19.5, or 3.20.0 to 3.20.1 (inclusive)
-
Verify Management Console accessibilityConfirm the Management Console login page is reachable at your_GHE_hostname/setup or /setup/unlockAffected if The Management Console login page is publicly or untrusted network accessible
-
Identify exposed Management Console URLCheck if the /setup/unlock endpoint is accessible externally by requesting it via browser or curlAffected if The endpoint responds with the login page and accepts query parameters
A defender is affected if their GitHub Enterprise Server version is within the ranges 3.19.1-3.19.5 or 3.20.0-3.20.1 AND the Management Console is accessible to untrusted users who could be tricked into clicking a malicious link.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.19.63.20.2
Upgrade GitHub Enterprise Server to version 3.19.6 or 3.20.2 or later. Users should be advised not to click suspicious links leading to the management console login page.
3.19.6 or later for 3.19.x branches; 3.20.2 or later for 3.20.x branches
- 1. Identify the current GitHub Enterprise Server version by checking the Management Console or running 'ghe-version' from the administrative shell
- 2. If running version 3.19.1 through 3.19.5, plan upgrade to version 3.19.6 or later
- 3. If running version 3.20.0 through 3.20.1, plan upgrade to version 3.20.2 or later
- 4. Review GitHub Enterprise Server upgrade prerequisites and schedule a maintenance window
- 5. Perform the upgrade following GitHub's standard upgrade procedures for your deployment method
- 6. After upgrade, verify the vulnerability is fixed by testing the /setup/unlock endpoint with a benign redirect_to parameter to confirm proper encoding
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8106 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data