# CVE-2023-26073: Memory corruption in n/a

> Heap-based buffer overflow in Samsung Exynos 5G modem codec allows attackers to execute arbitrary code or escalate privileges via crafted messages.

- **Severity:** High 7.6 (`CVSS:3.1/AC:L/AV:N/A:H/C:L/I:L/PR:L/S:U/UI:N`)
- **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:** 13 Mar 2023
- **Updated:** 3 Mar 2025
- **Also known as:** A-269656813, GHSA-q978-xx62-9w9r, PUB-A-269656813

## What is CVE-2023-26073?

CVE-2023-26073 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 13 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Samsung Mobile Chipset and Baseband Modem Chipset for Exynos 850, Exynos 980, Exynos 1080, Exynos 1280, Exynos 2200, Exynos Modem 5123, Exynos Modem 5300, and Exynos Auto T5123. A heap-based buffer overflow in the 5G MM message codec can occur due to insufficient parameter validation when decoding the extended emergency number list.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-26073?

It affects 9 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 2200 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos 980 Firmware, Samsung Exynos Auto T5123 Firmware, Samsung Exynos Modem 5123 Firmware, Samsung Exynos Modem 5300 Firmware, Samsung Exynos W920 Firmware.

## How do I fix CVE-2023-26073?

Apply the vendor's patch.

## Is CVE-2023-26073 being exploited?

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

## Other vulnerabilities in Samsung Exynos 1080 Firmware

- [CVE-2025-54328](https://insights.sbomify.com/CVE-2025-54328/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-62818](https://insights.sbomify.com/CVE-2025-62818/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-58349](https://insights.sbomify.com/CVE-2025-58349/): Denial of service in n/a (critical 9.1)
- [CVE-2025-27807](https://insights.sbomify.com/CVE-2025-27807/): Memory corruption in n/a (critical 9.1)
- [CVE-2025-47202](https://insights.sbomify.com/CVE-2025-47202/): Memory corruption in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26073 and fix it if it is affected.

What it is: CVE-2023-26073 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 13 Mar 2023. 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-2023-26073 exists.

Affected product: Samsung Exynos 1080 Firmware. 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-2023-26073/ (Markdown: https://insights.sbomify.com/CVE-2023-26073/index.md)
```

## Sources

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

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