# CVE-2026-24091: Improper Validation of Syntactic Correctness of Input in Display

> Memory corruption in Qualcomm Snapdragon fastboot processing allows attackers to execute arbitrary code or escalate privileges.

- **Severity:** High 7.2 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** 4416730, A-489079565, ASB-A-489079565, GHSA-6gj5-936c-vhwv

## What is CVE-2026-24091?

CVE-2026-24091 is a high-severity memory corruption vulnerability in Qualcomm Apq8098 Firmware, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption while processing fastboot commands with improperly formatted input.

Weakness: CWE-1286 (Improper Validation of Syntactic Correctness of Input)

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

It affects 273 products.


Products: Qualcomm 5g Fixed Wireless Access Platform Firmware, Qualcomm Apq8098 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm C-V2x 9150 Firmware, Qualcomm Cologne Firmware, Qualcomm Cq7790 Firmware, Qualcomm Cq8725s Firmware, Qualcomm Cq8750m Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Flight Rb5 5g Platform Firmware, Qualcomm Fsm100 Platform Firmware, Qualcomm Fwa Gen 3 Ultra Firmware and 253 more.

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

Apply the vendor's patch.

## Is CVE-2026-24091 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8098 Firmware

- [CVE-2026-21385](https://insights.sbomify.com/CVE-2026-21385/): Qualcomm Multiple Chipsets Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2026-25268](https://insights.sbomify.com/CVE-2026-25268/): Stack-based Buffer Overflow in WLAN Host (high 8.8)
- [CVE-2025-47392](https://insights.sbomify.com/CVE-2025-47392/): Integer Overflow or Wraparound in GPS (high 8.8)
- [CVE-2026-25267](https://insights.sbomify.com/CVE-2026-25267/): Missing Authorization in Core (high 7.8)
- [CVE-2025-47379](https://insights.sbomify.com/CVE-2025-47379/): Use After Free in Automotive Audio (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24091 is a high-severity memory corruption vulnerability in Qualcomm Apq8098 Firmware, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24091 in the wild and no public exploit code.

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

## Sources

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

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