CVE-2025-52572: hikariatama Hikka · Improper Authentication
Affects hikariatama HikkaSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhikariatama/Hikkapkg:github/hikariatama/HikkaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately implement the following specific mitigations: 1) Deploy the Hikka userbot with the --no-web flag to disable the vulnerable web interface entirely, preventing unauthorized access. 2) If web interface use is necessary, restrict access via network-level controls such as firewall rules or VPNs to trusted IP addresses only, and close the web interface port immediately after authorization. 3) Educate users and administrators not to click "Allow" on any authentication prompts unless they explicitly initiated the action, reducing the risk of social engineering exploitation. 4) Monitor network traffic and logs for unusual authorization attempts or unexpected web interface activity. 5) Consider isolating userbot servers in segmented network zones to limit potential lateral movement if compromised. 6) Maintain up-to-date backups and incident response plans tailored to potential remote code execution scenarios. 7) Engage with the Hikka community or vendor for updates and patches, and plan for rapid deployment once available. 8) Conduct regular security assessments of Telegram automation tools and their interfaces to identify similar risks proactively.
Description
Hikka, a Telegram userbot, has vulnerability affects all users on all versions of Hikka. Two scenarios are possible.1. Web interface does not have an authenticated session: attacker can use his own Telegram account to gain RCE to the server by authorizing in the dangling web interface.2. Web interface does have an authenticated session: due to insufficient warning in the authentication message, users were tempted to click "Allow" in the "Allow web application ops" menu. This gave an attacker access not only to remote code execution, but also to Telegram accounts of owners. Scenario number 2 is known to have been exploited in the wild. No known patches are available, but some workarounds are available. Use `--no-web` flag and do not start userbot without it; after authorizing in the web interface, close the port on the server and/or start the userbot with `--no-web` flag; and do not click "Allow" in your helper bot unless it is your explicit action that needs to be allowed.