# CVE-2026-75892: Out of bounds write in PDP ctx GSN-Address decode

> An out-of-bounds write in osmo-ggsn allows attackers to cause memory corruption, potentially leading to code execution or service disruption.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-mp35-rp3g-prrg, UBUNTU-CVE-2026-75892

## What is CVE-2026-75892?

CVE-2026-75892 is a medium-severity memory corruption vulnerability in Osmocom osmo-ggsn, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In osmo-ggsn 1.14.0 an out of bounds write issue was found in the gtp_decode_pdp_ctx() function through the PDP context GSN-Address sub-field, leading to memory corruption.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-75892 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75892 is a medium-severity memory corruption vulnerability in Osmocom osmo-ggsn, published on 18 Sep 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-75892 in the wild and no public exploit code.

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

## Sources

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

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