dbcve.org
Enterprise ServerApplication · GitHub

CVE-2026-8606

MEDIUM · 5.9 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 3.16.19 / 3.17.16 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an attacker to cause the server to issue HTTP requests to internal services via the security advisories package lookup feature. By directing requests to an internal management service and measuring response timing, an attacker could infer the values of sensitive environment variables, including signing secrets and private keys. Exploitation required GitHub Packages to be enabled; on instances not running in private mode the vulnerability was exploitable without authentication, otherwise any authenticated user could exploit it. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21.1 and was fixed in versions 3.20.3, 3.19.7, 3.18.10, 3.17.16, and 3.16.19. 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 confidence

A Server-Side Request Forgery (SSRF) vulnerability in GitHub Enterprise Server's security advisories package lookup feature allows unauthenticated attackers (or any authenticated user on private-mode instances) to cause the server to make HTTP requests to internal services. By timing responses from internal management services, attackers can infer sensitive environment variables including signing secrets and private keys.

MitigationUpgrade GitHub Enterprise Server to version 3.20.3, 3.19.7, 3.18.10, 3.17.16, or 3.16.19 or later. As a compensating control, disable GitHub Packages if unused or implement network segmentation to restrict internal service access.

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
Affected:< 3.16.19>= 3.17.0, < 3.17.16>= 3.18.0, < 3.18.10>= 3.19.0, < 3.19.7>= 3.20.0, < 3.20.3= 3.21.0

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GitHub Enterprise Server deployment
    Identify whether GitHub Enterprise Server is running in your environment by checking for the product or consulting your infrastructure inventory.
    Affected if GitHub Enterprise Server is deployed and the version falls within the affected ranges below.
  2. Determine the installed GitHub Enterprise Server version
    Use the administrative interface or management console to retrieve the current GitHub Enterprise Server version number.
    Affected if The installed version is: < 3.16.19, >= 3.17.0 and < 3.17.16, >= 3.18.0 and < 3.18.10, >= 3.19.0 and < 3.19.7, >= 3.20.0 and < 3.20.3, or exactly 3.21.0.
  3. Verify if GitHub Packages is enabled
    Check the GitHub Enterprise Server administrative settings to determine whether the Packages feature is currently enabled.
    Affected if GitHub Packages is enabled and the version is within the affected ranges listed above.
  4. Determine if unauthenticated access is permitted
    Review the security settings for the security advisories feature to identify whether non-private (public) mode allows unauthenticated package lookup requests.
    Affected if The environment allows unauthenticated access to the security advisories package lookup feature and the version is affected.

You are affected if GitHub Enterprise Server is running a version within the affected ranges AND GitHub Packages is enabled, allowing the SSRF vulnerability to be exploited via the security advisories package lookup feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.16.19 / 3.17.16 / 3.18.10 or later
Fixed in 3.16.193.17.163.18.10
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.20.3, 3.19.7, 3.18.10, 3.17.16, or 3.16.19 or later. As a compensating control, disable GitHub Packages if unused or implement network segmentation to restrict internal service access.

Recommended fix High confidence

3.16.19, 3.17.16, 3.18.10, or 3.19.7 (depending on your current release branch)

  1. 1. Identify the current GitHub Enterprise Server version by running `ghe-version` or checking the admin console.
  2. 2. Determine the appropriate upgrade path based on current version: if < 3.16.19, upgrade to 3.16.19; if >= 3.17.0 and < 3.17.16, upgrade to 3.17.16; if >= 3.18.0 and < 3.18.10, upgrade to 3.18.10; if >= 3.19.0 and < 3.19.7, upgrade to 3.19.7.
  3. 3. Before upgrading, review the upgrade prerequisites and backup procedures in the GitHub Enterprise Server documentation.
  4. 4. Perform the upgrade following the standard GitHub Enterprise Server upgrade procedure using the appropriate release asset from github.com/enterprise/enterprise.
  5. 5. After upgrade, verify the new version is running with `ghe-version`.
  6. 6. As a defense-in-depth measure, if GitHub Packages is not required, disable it in the admin console under 'Site admin > Packages > Settings'.
  7. 7. Review audit logs for any suspicious requests to internal services that occurred prior to patching.
Caveat Standard GitHub Enterprise Server upgrade considerations apply - review release notes for deprecations and test in staging before production deployment

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8606 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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