# CVE-2022-21669: Bot token exposed in main.py

> Attackers can access the exposed bot token to take over the Telegram bot and potentially read or modify group data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-cxgr-xpmj-9qjm

## What is CVE-2022-21669?

CVE-2022-21669 is a critical vulnerability in PuddingBot pudding-bot, published on 11 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PuddingBot is a group management bot. In version 0.0.6-b933652 and prior, the bot token is publicly exposed in main.py, making it accessible to malicious actors. The bot token has been revoked and new version is already running on the server. As of time of publication, the maintainers are planning to update code to reflect this change at a later date.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-21669?

It affects 1 product.


Products: Puddingbot Project Puddingbot.

## How do I fix CVE-2022-21669?

No fix has been published for CVE-2022-21669 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-21669 being exploited?

There is no known exploitation of CVE-2022-21669 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21669 and fix it if it is affected.

What it is: CVE-2022-21669 is a critical vulnerability in PuddingBot pudding-bot, published on 11 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21669 in the wild and no public exploit code.

Affected product: PuddingBot pudding-bot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21669/ (Markdown: https://insights.sbomify.com/CVE-2022-21669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21669
- OSV: https://osv.dev/vulnerability/CVE-2022-21669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21669/
Summaries are generated and may contain mistakes; the official description above is the record.