Out of bounds write in PDP ctx GSN-Address decode

published 2026-09-18 51 d ago modified 2026-09-21 48 d ago also EUVD-2026-83271

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits: 0; none known

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.

Patch / fix

links 1

cgit.osmocom.org/osmo-ggsn/commit/?id=6c322f4dd339401a437da3c89c95f2bf64bca… commit

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 48 d ago (2026-09-21)

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

Osmocom osmo-ggsn

Classification

Weakness

CWE-787 Out-of-bounds Write

References

cgit.osmocom.org /osmo-ggsn/commit/?id=6c322f4dd339401a437da3c89c95f2bf64bca995
patch, mitigation

Sources

CVE List CVE-2026-75892
NVD CVE-2026-75892

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary