CVE-2025-55449 AstrBot is vulnerable to RCE with hard-coded JWT signing keys

High 7.3 Published 8 May 2026 Updated 8 May 2026

AstrBot uses a hardcoded private key for JWT signing, allowing attackers to forge tokens and bypass authentication or take over accounts.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2025-55449?

CVE-2025-55449 is a high-severity vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

AstrBotDevs AstrBot 3.5.15 has Advanced_System_for_Text_Response_and_Bot_Operations_Tool as the hardcoded private key used to sign a JWT.

Weakness: CWE-321

Which versions are affected by CVE-2025-55449?

3 open source packages ship an affected version, including astrbot. It affects 1 product.

Package	Affected	Fixed in
`astrbot` PyPI	All versions	`3.5.18`
`astrbot` PyPI	All versions	`3.5.18`
`astrbot` PyPI	All versions	`3.5.18`

Products include Astrbot Astrbot.

How do I fix CVE-2025-55449?

Upgrade astrbot to 3.5.18 or later.

Is CVE-2025-55449 being exploited?

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

Public exploit code: 2 proofs of concept on GitHub.

Sources

Also known as GHSA-4m32-cjv7-f425, PYSEC-2026-285.