Quick answers
- Is CVE-2026-75892 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75892 being exploited in the wild.
- How severe is CVE-2026-75892?
- Medium severity, with a CVSS score of 6.5, published 18 September 2026.
- Which products and versions are affected?
- Osmocom Osmo-Ggsn 1.14.0; Osmocom Osmo-Sgsn <UNKNOWN>.
- Is there a fix for CVE-2026-75892?
- A patch was published on 2026-08-12: Fix committed to osmo-ggsn repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75892 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75892?
- Check whether you run Osmocom Osmo-Ggsn or Osmocom Osmo-Sgsn at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The gtp_decode_pdp_ctx() function in osmo-ggsn and osmo-sgsn's libgtp library fails to validate GSN-Address sub-field lengths against the 16-byte destination buffer before performing memcpy(), allowing lengths up to 255 bytes from the wire to overflow the fixed array. The vulnerability is exploitable over the Gn/Gp interface by a malicious or spoofed peer GSN through SGSN Context Response or Forward Relocation messages. A fix validating lengths against destination capacity is available.
Affected products
- osmocom osmo-ggsn 1.14.0
- osmocom osmo-sgsn <UNKNOWN>
Timeline
- 2026-09-18: disclosed
- 2026-08-12: patched: Fix committed to osmo-ggsn repository