CVE-2022-21669Network attack vector

Bot impersonation via hard-coded Telegram token

Published Jan 11, 2022 · Updated Apr 23, 2025

Hard-coded credentials in PuddingBot 0.0.6-b933652 and earlier allow remote attackers to obtain its Telegram bot token from public source code. In main.py, a literal token is passed to the Telegram Bot constructor inside the commented get_commands_command function, publishing an active credential in the repository. Access requires only reading the public repository; possession of the token permits authentication as the bot and unauthorized bot actions.

CVSS severity9.1
Critical
EPSS probability1.03%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded credentials in PuddingBot 0.0.6-b933652 and earlier allow remote attackers to obtain its Telegram bot token from public source code. In main.py, a literal token is passed to the Telegram Bot constructor inside the commented get_commands_command function, publishing an active credential in the repository. Access requires only reading the public repository; possession of the token permits authentication as the bot and unauthorized bot actions.

The record

CVE
CVE-2022-21669
Published
Jan 11, 2022
Updated
Apr 23, 2025
Vendor
PuddingBot
Product
PuddingBot
Classifications
CWE-798, T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 11, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=<= 0.0.6-b933652

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

PuddingBot · PuddingBotversion=<= 0.0.6-b933652

Published CVSS scores

5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
9.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-798Use of Hard-coded Credentials
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo