Enterprise ServerApplication · GitHub
CVE-2022-46258
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 incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a repository-scoped token with read/write access to modify Action Workflow files without a Workflow scope. The Create or Update file contents API should enforce workflow scope. This vulnerability affected all versions of GitHub Enterprise Server prior to version 3.7 and was fixed in versions 3.3.16, 3.4.11, 3.5.8, and 3.6.4. 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 confidenceGitHub Enterprise Server allowed repository-scoped tokens with read/write access to modify GitHub Actions workflow files via the Create or Update file contents API without enforcing the required Workflow scope. This authorization bypass enabled tokens that should only have repository access to alter sensitive workflow configurations.
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.16>= 3.4.0, < 3.4.11>= 3.5.0, < 3.5.8>= 3.6.0, < 3.6.4CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 your GitHub Enterprise Server versionNavigate to the GitHub Enterprise Server administration console or check the /setup/settings page to view the current version. Alternatively, use the administrative API endpoint: GET /enterprise/settings or check the About page in the management console.Affected if The installed version is less than 3.3.16, between 3.4.0 and 3.4.11, between 3.5.0 and 3.5.8, or between 3.6.0 and 3.6.4.
-
Review existing personal access tokens and OAuth tokensUse the site admin API to list all tokens or have administrators review tokens in their organization settings. Look for tokens with repo scope (read/write repository access) that do not have the workflow scope explicitly granted.Affected if Repository-scoped tokens exist that have read/write access to repositories but lack the workflow scope, and the GitHub Enterprise Server version is in the affected range.
-
Verify workflow file modification attempts via APIAudit API logs or use the GitHub Enterprise Server audit log to search for Create or Update file API calls targeting .github/workflows/ directories. Look for events where the actor used a token without workflow scope.Affected if Workflow files were modified using tokens that only had repository read/write access without the workflow scope.
-
Check audit log for unauthorized workflow accessQuery the enterprise audit log filtering for the 'update_workflow' or 'push' events involving paths under .github/workflows/ and review the token scopes used for those actions.Affected if Workflow modifications were performed by users or integrations using tokens scoped only to repository access.
You are affected if your GitHub Enterprise Server version falls within the vulnerable ranges AND repository-scoped tokens without explicit workflow scope were able to modify workflow files.
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.163.4.113.5.8
Upgrade GitHub Enterprise Server to version 3.3.16, 3.4.11, 3.5.8, 3.6.4, or later. Review existing token scopes and revoke or adjust any tokens that may have inappropriately accessed workflow files prior to the fix.
Upgrade to version 3.7 (latest fixed release) or the appropriate point release: 3.3.16, 3.4.11, 3.5.8, or 3.6.4 depending on your current branch
- 1. Identify the current GitHub Enterprise Server version by navigating to the Management Console or using the administrative API
- 2. Determine which upgrade path applies based on current version: if < 3.3.x upgrade to 3.3.16; if 3.4.x upgrade to 3.4.11; if 3.5.x upgrade to 3.5.8; if 3.6.x upgrade to 3.6.4
- 3. Review GitHub Enterprise Server upgrade prerequisites and backup requirements from docs.github.com
- 4. Perform the upgrade following the standard GitHub Enterprise Server upgrade procedure
- 5. After upgrade, verify the instance is functioning correctly
- 6. Confirm the vulnerability is remediated by testing that repository-scoped tokens without Workflow scope can no longer modify Action Workflow files via the Create or Update file contents API
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-46258 — 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-46258 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