{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75892 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75892 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-75892 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-75892 in the wild and no public exploit code.\n\nAffected product: Osmocom osmo-ggsn. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-75892/ (Markdown: https://insights.sbomify.com/CVE-2026-75892/index.md)","id":"CVE-2026-75892","markdown":"https://insights.sbomify.com/CVE-2026-75892/index.md","name":"CVE-2026-75892","record":{"aliases":["GHSA-mp35-rp3g-prrg","UBUNTU-CVE-2026-75892"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"GGSN server software","requires_auth":"none","summary":"An out-of-bounds write in osmo-ggsn allows attackers to cause memory corruption, potentially leading to code execution or service disruption.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat-cnalr","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Out of bounds write in PDP ctx GSN-Address decode","id":"CVE-2026-75892","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Heap based buffer overflow at ipaccess_proxy_read_msg()","id":"CVE-2026-75893"},"packages":[],"prev":{"headline":"The Kirki plugin for WordPress is vulnerable to Privilege Escalation via PHP Object Injection in all versions up to, and including, 6.2.5 vi","id":"CVE-2026-75891"},"products":["osmo-ggsn"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["Osmocom"]},"summary":"An out-of-bounds write in osmo-ggsn allows attackers to cause memory corruption, potentially leading to code execution or service disruption.","url":"https://insights.sbomify.com/CVE-2026-75892/"}