Enterprise ServerApplication · GitHub
CVE-2022-46256
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 path traversal vulnerability was identified in GitHub Enterprise Server that allowed remote code execution when building a GitHub Pages site. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the instance. This vulnerability was fixed in versions 3.3.17, 3.4.12, 3.5.9, 3.6.5 and 3.7.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 confidenceA path traversal vulnerability in GitHub Enterprise Server's GitHub Pages site building functionality allows authenticated users with Pages creation permissions to perform path traversal attacks, leading to remote code execution on the server. The vulnerability exists in the Pages build process and was fixed in multiple point releases.
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.3.17>= 3.4.0, < 3.4.12>= 3.5.0, < 3.5.9>= 3.6.0, < 3.6.5>= 3.7.0, < 3.7.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Determine GitHub Enterprise Server versionAccess the GitHub Enterprise Server admin console and navigate to the Site Admin dashboard, or check the version file at /etc/github/enterprise-release. Alternatively, use the administrative API endpoint /api/v3/enterprise/meta.Affected if The installed version falls into any of these ranges: < 3.3.17, >= 3.4.0 and < 3.4.12, >= 3.5.0 and < 3.5.9, >= 3.6.0 and < 3.6.5, or >= 3.7.0 and < 3.7.2
-
Verify if GitHub Pages is enabledIn the GitHub Enterprise Server admin console, go to Settings > Pages, or query the enterprise settings API to check if Pages site building functionality is enabled for the instance.Affected if GitHub Pages feature is enabled on the instance
-
Check Pages site creation permissionsReview the Pages settings at the organization or repository level to determine which users or teams have permissions to create GitHub Pages sites. In the admin console, examine the Pages access controls and any site creation policies.Affected if Any users other than site administrators have permissions to create or build GitHub Pages sites
-
Inspect Pages build logsAccess the GitHub Enterprise Server management console audit logs or Pages service logs. Look for build events and check if the build process handles source files in a way that could allow path traversal (look for unusual file access patterns or build failures).Affected if Audit logs show Pages builds that access paths outside the expected repository content directory
You are affected if your GitHub Enterprise Server version is within the vulnerable ranges AND GitHub Pages is enabled with non-administrative users having Pages creation permissions.
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.3.173.4.123.5.9
Upgrade GitHub Enterprise Server to version 3.3.17, 3.4.12, 3.5.9, 3.6.5, or 3.7.2 or later. Review and restrict GitHub Pages site creation permissions to minimize attack surface.
Upgrade to version 3.7.2 or later (the latest 3.7.x release). If staying on older branches, minimum fixed versions are: 3.3.17, 3.4.12, 3.5.9, or 3.6.5.
- Backup your GitHub Enterprise Server data and configuration before proceeding with any upgrade.
- Identify your current GitHub Enterprise Server version by navigating to the admin console or running: ghe-version
- Consult the GitHub Enterprise Server upgrade documentation at docs.github.com for your specific upgrade path.
- If currently on version < 3.3.17, upgrade to 3.3.17 or later (preferably 3.7.x for latest security fixes).
- If currently on version 3.4.x (where 3.4.0 <= version < 3.4.12), upgrade to 3.4.12 or later (preferably 3.7.x).
- If currently on version 3.5.x (where 3.5.0 <= version < 3.5.9), upgrade to 3.5.9 or later (preferably 3.7.x).
- If currently on version 3.6.x (where 3.6.0 <= version < 3.6.5), upgrade to 3.6.5 or later (preferably 3.7.x).
- Follow the standard GitHub Enterprise Server upgrade procedure using the admin console or command-line utilities.
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-2022-46256 — 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-2022-46256 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