# CVE-2026-7779: Denial of service in Open5GS

> Remote attackers can cause a denial of service in Open5GS by manipulating the authentication-subscription endpoint, affecting 5G core network availability.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-c78f-m7pg-c3p7

## What is CVE-2026-7779?

CVE-2026-7779 is a medium-severity denial of service vulnerability in Open5GS, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in Open5GS up to 2.7.7. Affected is the function udm_nudr_dr_handle_subscription_authentication of the file /src/udm/nudr-handler.c of the component authentication-subscription Endpoint. Performing a manipulation results in denial of service. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-7779 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7779 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7779 is a medium-severity denial of service vulnerability in Open5GS, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7779 exists.

Affected product: Open5GS. 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-7779/ (Markdown: https://insights.sbomify.com/CVE-2026-7779/index.md)
```

## Sources

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

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