Quick answers
- Is CVE-2026-75893 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75893 being exploited in the wild.
- How severe is CVE-2026-75893?
- High severity, with a CVSS score of 7.5, published 18 September 2026.
- Which products and versions are affected?
- Osmocom Osmo-Bsc 1.0.1 through 1.14.1.
- Is there a fix for CVE-2026-75893?
- A patch was published on 2026-08-07: Fix committed to master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75893 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-75893?
- Check whether you run Osmocom Osmo-Bsc 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
A heap buffer overflow exists in the ipaccess_proxy_read_msg() function due to insufficient validation of IPA frame length fields. The function reads a 16-bit length value from the wire header and uses it directly in recv() without checking against the fixed 1200-byte msgb allocation, allowing an attacker to write past the heap buffer boundary via network-sourced frames.
Affected products
- Osmocom osmo-bsc 1.0.1 through 1.14.1
Timeline
- 2026-09-18: disclosed
- 2026-08-07: patched: Fix committed to master branch