# CVE-2026-82608: Kamailio AVP cxdx_avp.c get_4bytes out-of-bounds

> Remote attackers can trigger an out-of-bounds read in Kamailio's AVP handler, potentially exposing memory or causing crashes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-82608, GHSA-cqrq-g7g6-656p, UBUNTU-CVE-2026-82608

## What is CVE-2026-82608?

CVE-2026-82608 is a medium-severity memory corruption vulnerability in Kamailio, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Kamailio up to 5.5.0/6.0.7. This affects the function get_4bytes of the file src/modules/ims_registrar_scscf/cxdx_avp.c of the component AVP Handler. Executing a manipulation can lead to out-of-bounds read. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. This patch is called abb5d60af6eefbd367bf6588c5589566b090e272. It is advisable to implement a patch to correct this issue. The vendor points out, that "[v]ersion 5.5.0 is old and not maintained anymore."

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2026-82608 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82608 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82608 is a medium-severity memory corruption vulnerability in Kamailio, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82608 exists.

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

## Sources

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

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