# CVE-2026-7541: Denial of service vulnerability in GitHub Enterprise Server allowed service disruption via unauthenticated API endpoint

> Unauthenticated attackers can cause service disruption in GitHub Enterprise Server by sending deeply nested JSON payloads to an API endpoint.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-3738-jvgh-jh3h

## What is CVE-2026-7541?

CVE-2026-7541 is a medium-severity denial of service vulnerability in Github Enterprise Server, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial of service vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause service disruption by sending crafted requests with deeply nested JSON payloads to an unauthenticated API endpoint. The endpoint parsed user-controlled JSON request bodies without size or depth limits, causing excessive CPU and memory consumption. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18. This vulnerability was reported via the GitHub Bug Bounty program.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-7541?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2026-7541?

No fix has been published for CVE-2026-7541 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7541 being exploited?

There is no known exploitation of CVE-2026-7541 in the wild and no public exploit code.

## Other vulnerabilities in Github Enterprise Server

- [CVE-2024-4985](https://insights.sbomify.com/CVE-2024-4985/): Auth bypass in Enterprise Server (critical 10.0)
- [CVE-2022-23739](https://insights.sbomify.com/CVE-2022-23739/): Missing authorization in GitHub Enterprise Server (critical 9.8)
- [CVE-2022-46255](https://insights.sbomify.com/CVE-2022-46255/): Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE (critical 9.8)
- [CVE-2021-22869](https://insights.sbomify.com/CVE-2021-22869/): Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group (critical 9.8)
- [CVE-2024-9487](https://insights.sbomify.com/CVE-2024-9487/): Auth bypass in Enterprise Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7541 and fix it if it is affected.

What it is: CVE-2026-7541 is a medium-severity denial of service vulnerability in Github Enterprise Server, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7541 in the wild and no public exploit code.

Affected product: Github Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7541/ (Markdown: https://insights.sbomify.com/CVE-2026-7541/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7541
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7541
- OSV: https://osv.dev/vulnerability/CVE-2026-7541

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7541/
Summaries are generated and may contain mistakes; the official description above is the record.