# CVE-2026-75895: Out of bounds read at smpp34_unpack()

> An out-of-bounds read in libsmpp34 allows attackers to cause memory corruption via crafted SMPP PDUs, potentially leading to code execution or crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-75895, GHSA-fpm9-38vr-4gp8, UBUNTU-CVE-2026-75895

## What is CVE-2026-75895?

CVE-2026-75895 is a high-severity memory corruption vulnerability in Osmocom libsmpp34, 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 libsmpp35 from 0.1.0 through 1.8.0 out of bound read issue was found in the at smpp34_unpack() function via attacker controlled SMPP PDUs, leading to memory corruption.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-75895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75895 is a high-severity memory corruption vulnerability in Osmocom libsmpp34, 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-75895 in the wild and no public exploit code.

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

## Sources

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

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