# CVE-2026-78157: Open5GS Rx AA-Request pcrf-rx-path.c pcrf_rx_aar_cb out-of-bounds

> Remote attackers can trigger an out-of-bounds read in Open5GS via Rx AA-Request, potentially causing information disclosure or service disruption.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-65jg-mq47-hgxf

## What is CVE-2026-78157?

CVE-2026-78157 is a medium-severity memory corruption vulnerability in Open5GS, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in Open5GS 2.8.0. This affects the function pcrf_rx_aar_cb of the file src/pcrf/pcrf-rx-path.c of the component Rx AA-Request Handler. Performing a manipulation results in out-of-bounds read. It is possible to initiate the attack remotely. The patch is named c18dc6938bf63cc7374315d3dca303d92066e746. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-78157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78157 is a medium-severity memory corruption vulnerability in Open5GS, published on 24 Aug 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-78157 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-78157/ (Markdown: https://insights.sbomify.com/CVE-2026-78157/index.md)
```

## Sources

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

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