Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_P

CVE-2026-77987: GitHub Enterprise Server notebook viewer vulnerable to Server-side request forgery

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.87% (FIRST EPSS); higher than 59% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: GitHub Enterprise Server 3.17.*, 3.17.21, 3.18.*.

Low priority for now. Upgrade to GitHub Enterprise Server 3.17.*, 3.17.21, 3.18.* or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server. The notebook viewer validated the scheme and host of a user-supplied URL but did not validate the port, allowing requests to be directed to internal services listening on other ports of the same appliance. Response bodies were not returned to the requester, but response timing acted as an oracle that allowed instance secrets to be extracted character by character. An extracted secret could then be used in a separate interaction with an internal service to obtain remote code execution on the appliance. Exploitation required network access to the instance and was unauthenticated when private mode was disabled, or required any authenticated user when private mode was enabled. This vulnerability affected GitHub Enterprise Server versions 3.17 through 3.22 and was fixed in versions 3.22.1, 3.21.6, 3.20.8, 3.19.12, 3.18.15, and 3.17.21. This vulnerability was reported through the GitHub Bug Bounty program.

CriticalCVSS 9.3 · v4.0—No exploit Fix available
Published
Sep 22, 2026
Updated
Oct 2, 2026
EPSS
0.8% · 59th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_P
9.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-77987

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
githubenterprise server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • github enterprise server3.17.0 and later · before 3.17.21
  • github enterprise server3.18.0 and later · before 3.18.15
  • github enterprise server3.19.0 and later · before 3.19.12
  • github enterprise server3.20.0 and later · before 3.20.8
  • github enterprise server3.21.0 and later · before 3.21.6
  • github enterprise server3.22.0 and later · before 3.22.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.

  • GitHub Enterprise Server

    • 3.17.0 and later · before 3.17.*affected · semverfixed in 3.17.21
    • 3.18.0 and later · before 3.18.*affected · semverfixed in 3.18.15
    • 3.19.0 and later · before 3.19.*affected · semverfixed in 3.19.12
    • 3.20.0 and later · before 3.20.*affected · semverfixed in 3.20.8
    • 3.21.0 and later · before 3.21.*affected · semverfixed in 3.21.6
    • 3.22.0 and later · before 3.22.*affected · semverfixed in 3.22.1

Other highest-scoring records for the same primary product.

  • CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
    61This week
  • CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
    55Plan
  • CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
    46Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-75101Sep 22, 2026 · Authorization bypass vulnerability in GitHub Enterprise Server allowed reading of private pull request diffs and patches via repository name collision
    24Monitor
  • ← EarlierCVE-2026-77912Sep 22, 2026 · Stored cross-site scripting vulnerability in GitHub Enterprise Server allowed HTML attribute injection via the Markdown rendering pipeline
    29Monitor
  • Later →CVE-2026-103620Oct 6, 2026 · Missing authorization in GitHub Enterprise Server allowed repository writers to replace default branches via GraphQL
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
GitHub Enterprise Server3.17.*Vendor (CNA)
GitHub Enterprise Server3.17.21Vendor (CNA)
GitHub Enterprise Server3.18.*Vendor (CNA)
GitHub Enterprise Server3.18.15Vendor (CNA)
GitHub Enterprise Server3.19.*Vendor (CNA)
GitHub Enterprise Server3.19.12Vendor (CNA)
GitHub Enterprise Server3.20.*Vendor (CNA)
GitHub Enterprise Server3.20.8Vendor (CNA)
GitHub Enterprise Server3.21.*Vendor (CNA)
GitHub Enterprise Server3.21.6Vendor (CNA)
GitHub Enterprise Server3.22.*Vendor (CNA)
GitHub Enterprise Server3.22.1Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records