# CVE-2026-7536: Open5GS BSF pcfBindings bsf_sess_add_by_ip_address denial of service

> Remote attackers can cause denial of service in Open5GS BSF by manipulating the ipv4Addr argument in pcfBindings.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-286x-7qf6-x2h4

## What is CVE-2026-7536?

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

### Official description

A vulnerability was determined in Open5GS up to 2.7.7. This vulnerability affects the function bsf_sess_add_by_ip_address of the file /nbsf-management/v1/pcfBindings of the component BSF. Executing a manipulation of the argument ipv4Addr can lead to denial of service. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. 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-7536?


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

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

## Is CVE-2026-7536 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7536 is a medium-severity denial of service vulnerability in Open5GS, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7536 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-7536/ (Markdown: https://insights.sbomify.com/CVE-2026-7536/index.md)
```

## Sources

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

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