Skip to main content
CVE-2025-52571VulnerabilityPublished

CVE-2025-52571: hikariatama Hikka · Improper Authentication

Affects hikariatama HikkaSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical : upgrade to 1.6.2 as a priority.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.6.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade hikariatama/Hikka to 1.6.2.

Affected software

ProductAffectedFixed in
GitHubhikariatama/Hikkapkg:github/hikariatama/HikkaOther threatsAffected
  • <1.6.2
Fixed in
  • 1.6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to Hikka version 1.6.2 or later is mandatory to patch the vulnerability. 2. Conduct an audit of all Telegram userbots deployed within the organization to identify any running vulnerable versions or forks. 3. Restrict server access and isolate servers running userbots from critical internal networks to limit potential lateral movement in case of compromise. 4. Implement multi-factor authentication (MFA) on Telegram accounts where possible to add an additional layer of protection, although this may not fully mitigate the vulnerability. 5. Monitor Telegram account activity for unusual behavior such as unexpected messages or login notifications. 6. Employ network-level monitoring and intrusion detection systems to detect anomalous traffic or command execution on servers hosting userbots. 7. Educate users and administrators about the risks of running outdated userbot software and the importance of timely updates. 8. Consider temporarily disabling userbots if immediate patching is not feasible, especially in high-risk environments. 9. Review and harden server configurations, including limiting permissions and applying the principle of least privilege to the userbot service accounts.

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.

References

Community reviews

Loading reviews…