CVE-2022-21669: PuddingBot is a group management bot
CVE-2022-21669 is a critical-severity flaw (CVSS 9.1) affecting puddingbot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.1 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.0% (top 36%) |
| CISA exploited list | No |
| Weakness | CWE-798 |
| Published | 2022-01-11 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-21669?
puddingbot: upgrade to newer than 0.0.6-b933652. Exact commands for each OS are on this page.
Is CVE-2022-21669 being exploited?
CVE-2022-21669 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-21669 affect?
CVE-2022-21669 affects puddingbot. Severity is critical (CVSS 9.1). 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 serve
How urgent is CVE-2022-21669?
Priority 53/100. Critical severity; Remotely exploitable, no login, no user action