Enterprise ServerApplication · GitHub
CVE-2025-14046
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 · uneditedAn improper neutralization of input vulnerability was identified in GitHub Enterprise Server that allowed user-supplied HTML to inject DOM elements with IDs that collided with server-initialized data islands. These collisions could overwrite or shadow critical application state objects used by certain Project views, leading to unintended server-side POST requests or other unauthorized backend interactions. Successful exploitation requires an attacker to have access to the target GitHub Enterprise Server instance and to entice a privileged user to view crafted malicious content that includes conflicting HTML elements. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18.3, 3.17.9, 3.16.12, 3.15.16, and 3.14.21.
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 confidenceThis is a DOM-based ID collision vulnerability where user-supplied HTML can create DOM elements with IDs that collide with server-initialized data islands in GitHub Enterprise Server Project views. These collisions overwrite or shadow critical application state objects, enabling attackers to trigger unauthorized server-side POST requests through a crafted page viewed by a privileged user.
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.14.21>= 3.15.0, < 3.15.16>= 3.16.0, < 3.16.12>= 3.17.0, < 3.17.9>= 3.18.0, < 3.18.3CVSS 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.
-
Identify GitHub Enterprise Server versionAccess the admin dashboard, go to the Site Admin page, or run 'ghe-version' from the command line if you have SSH access to the instanceAffected if The installed version falls into one of the affected ranges: < 3.14.21, >= 3.15.0 and < 3.15.16, >= 3.16.0 and < 3.16.12, >= 3.17.0 and < 3.17.9, or >= 3.18.0 and < 3.18.3
-
Determine if GitHub Projects is enabledCheck the Enterprise settings or Organization settings to verify if Projects (specifically Project views) are available or have been createdAffected if Projects feature is active and Project views exist in the environment
-
Assess user content injection risk in ProjectsReview any integrations, workflows, or external services that can submit or render user-supplied HTML content within Project view pagesAffected if User-controlled or externally-sourced HTML can be rendered within the context of Project views, allowing ID collision with server data islands
-
Verify data island usage in Project viewsInspect the HTML source of a Project view page in a browser developer tool and look for elements with IDs that correspond to server-initialized data (such as form submissions or state objects)Affected if The page contains data island elements with IDs that could be overwritten by user-supplied HTML with matching IDs
If the installed version is within any of the affected ranges and Project views are accessible to users who can supply HTML content, the environment is vulnerable to ID collision attacks.
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.14.213.15.163.16.12
Upgrade GitHub Enterprise Server to version 3.18.3, 3.17.9, 3.16.12, 3.15.16, or 3.14.21 or later. Additionally, implement input validation and ensure user-controlled HTML cannot access the server data island ID namespace.
Upgrade to 3.14.21, 3.15.16, 3.16.12, 3.17.9, or 3.18.3 (depending on your current release branch)
- 1. Identify the current GitHub Enterprise Server version by navigating to the admin console or running: ghe-version
- 2. Determine the appropriate target version based on current release line: if on 3.14.x upgrade to 3.14.21; if on 3.15.x upgrade to 3.15.16; if on 3.16.x upgrade to 3.16.12; if on 3.17.x upgrade to 3.17.9; if on earlier versions upgrade to 3.18.3
- 3. Review GitHub Enterprise Server upgrade prerequisites and backup requirements at docs.github.com
- 4. Create a backup or snapshot of the current instance before upgrading
- 5. Download the appropriate upgrade package from GitHub Enterprise downloads
- 6. Follow the standard GitHub Enterprise Server upgrade procedure for your installation method (Hotupgrade or Backup/Restore)
- 7. After upgrade, verify the version by checking: ghe-version
- 8. Confirm the upgrade was successful by logging into the admin console and reviewing system status
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14046 — 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-2025-14046 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