Enterprise ServerApplication · GitHub
CVE-2025-11892
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 allows DOM-based cross-site scripting via Issues search label filter that could lead to privilege escalation and unauthorized workflow triggers. Successful exploitation requires an attacker to have access to the target GitHub Enterprise Server instance and to entice a user, while operating in sudo mode, to click on a crafted malicious link to perform actions that require elevated privileges. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18.1, 3.17.7, 3.16.10, 3.15.14, 3.14.19.
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 confidenceDOM-based XSS vulnerability in GitHub Enterprise Server's Issues search label filter allows injection of malicious scripts via crafted URLs. When a user in sudo (elevated privileges) mode clicks the malicious link, the attacker can achieve privilege escalation and trigger unauthorized workflow actions.
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.19>= 3.15.0, < 3.15.14>= 3.16.0, < 3.16.10>= 3.17.0, < 3.17.7= 3.18.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 versionRun `ghe-version` command in the GitHub Enterprise management shell, or check the Management Console dashboard under 'About' sectionAffected if The installed version falls within any of these ranges: < 3.14.19, >= 3.15.0 and < 3.15.14, >= 3.16.0 and < 3.16.10, >= 3.17.0 and < 3.17.7, or equals 3.18.0
-
Verify Issues search functionality is accessibleNavigate to any repository on the GitHub Enterprise instance and access the Issues tab. Confirm the search bar with label filtering (clicking a label or using is:issue label: syntax) loads without errorsAffected if The Issues search feature is accessible to users on the instance (this is the attack surface for the XSS)
-
Confirm sudo mode is enabled for the instanceCheck the Management Console under 'Security' settings, or attempt to access sudo mode by typing sudo in the management shell or checking if enterprise administrators have elevated sudo privileges availableAffected if Sudo mode is available on the GitHub Enterprise Server instance (required for the privilege escalation aspect of this vulnerability)
-
Inspect browser for XSS indicators on Issues searchAs an administrator, use a test account to access the Issues search with a label parameter (example: /issues?labels=test). Open browser developer tools and inspect the DOM for unsanitized reflection of the label parameter valueAffected if Label parameter values from the URL are reflected directly into the HTML without sanitization
The environment is affected if running a vulnerable GitHub Enterprise Server version (as identified in step 1) AND the Issues search label filter is accessible AND sudo mode is enabled on the instance.
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.193.15.143.16.10
Upgrade GitHub Enterprise Server to version 3.18.1, 3.17.7, 3.16.10, 3.15.14, 3.14.19 or later. Advise administrators to avoid clicking untrusted links while in sudo mode.
Upgrade to GitHub Enterprise Server 3.18.1 (or the latest 3.x release available), or at minimum to the fixed version for your current branch: 3.14.19, 3.15.14, 3.16.10, or 3.17.7
- 1. Identify the current GitHub Enterprise Server version by navigating to the admin dashboard or running: ghe-version
- 2. Based on the current version, determine the appropriate upgrade path to one of the fixed releases: 3.14.19, 3.15.14, 3.16.10, 3.17.7, or 3.18.1
- 3. Review the GitHub Enterprise Server upgrade documentation for your specific version path
- 4. Create a complete backup of the GitHub Enterprise Server instance before upgrading
- 5. Follow the standard GitHub Enterprise Server upgrade procedure using the appropriate upgrade package for your target fixed version
- 6. After upgrade completion, verify the version matches the expected fixed release using: ghe-version
- 7. Test that the Issues search label filter functionality works correctly and that the XSS vulnerability is no longer present
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-2025-11892 — 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-11892 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