# CVE-2026-21095: Memory corruption in Samsung Mobile Devices

> Remote attackers can execute arbitrary code via a heap-based buffer overflow in the DNG decoder on Samsung mobile devices.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-fgp3-964j-h4rh

## What is CVE-2026-21095?

CVE-2026-21095 is a critical memory corruption vulnerability in Samsung Android, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in DNG decoder of libimagecodec.quram.so prior to SMR Sep-2026 Release 1 allows remote attackers to execute arbitrary code.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Samsung Android.

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

No fix has been published for CVE-2026-21095 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-21095 being exploited?

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

## Other vulnerabilities in Samsung Android

- [CVE-2025-21042](https://insights.sbomify.com/CVE-2025-21042/): Samsung Mobile Devices Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2025-21043](https://insights.sbomify.com/CVE-2025-21043/): Samsung Mobile Devices Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2021-25487](https://insights.sbomify.com/CVE-2021-25487/): Samsung Mobile Devices Out-of-Bounds Read (high 7.3, exploited in the wild)
- [CVE-2021-25394](https://insights.sbomify.com/CVE-2021-25394/): Samsung Mobile Devices Race Condition (medium 6.4, exploited in the wild)
- [CVE-2021-25395](https://insights.sbomify.com/CVE-2021-25395/): Samsung Mobile Devices Race Condition (medium 6.4, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21095 is a critical memory corruption vulnerability in Samsung Android, published on 9 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-21095 in the wild and no public exploit code.

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

## Sources

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

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