CVE-2025-55449

Hardcoded Private Key Enables JWT Forgery in AstrBot

Published May 8, 2026 CVSS 3.1 · 7.3 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

AstrBotDevs AstrBot 3.5.15 contains a hardcoded private key named Advanced_System_for_Text_Response_and_Bot_Operations_Tool that is used to sign JSON Web Tokens. This usage constitutes a CWE‑321 weakness – the use of a hard‑coded secret value. Attackers who can construct their own JWTs with this key can impersonate legitimate users or services, bypass authentication, and potentially execute commands or alter the bot’s behavior, leading to remote code execution.

Affected Systems

The affected product is AstrBotDevs AstrBot, specifically version 3.5.15. No other vendors or product versions are known to be impacted. The hardcoded private key exists within the Advanced_System_for_Text_Response_and_Bot_Operations_Tool component of this release.

Risk and Exploitability

The EPSS score (< 1%) indicates a low but non‑zero probability of exploitation. Accordingly, the risk is primarily associated with environments where AstrBot services are exposed to network traffic and lack additional authentication or token revocation mechanisms. Attackers would need to generate a valid JWT and send it to the API, elevating privileges and potentially triggering arbitrary code execution if the bot performs privileged actions based on token claims. The vulnerability is not listed in CISA KEV, and the CVSS score of 7.3 reflects a high severity risk for affected environments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest AstrBot release where the private key is no longer hardcoded or is securely stored.
  • Regenerate and rotate all JWT secret keys, reissuance of tokens, and enforce strict signature verification.
  • Restrict network access to AstrBot services and implement role‑based access control to minimize the blast radius of forged tokens.

Generated by OpenCVE AI on May 8, 2026 at 23:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4m32-cjv7-f425 AstrBot is vulnerable to RCE with hard-coded JWT signing keys
History
Type Values Removed Values Added
CPEs cpe:2.3:a:astrbot:astrbot:3.5.15:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Astrbot
Astrbot astrbot
Vendors & Products Astrbot
Astrbot astrbot
Type Values Removed Values Added
Title Hardcoded Private Key Enables JWT Forgery in AstrBot
Type Values Removed Values Added
Title Hardcoded Private Key in AstrBot Enables JWT Forgery and Potential Remote Code Execution
Weaknesses CWE-285
CWE-798
Type Values Removed Values Added
Weaknesses CWE-321
Metrics cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Hardcoded Private Key in AstrBot Enables JWT Forgery and Potential Remote Code Execution
Weaknesses CWE-285
CWE-798
Type Values Removed Values Added
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.
References
Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
May 8, 2026, 5:52 PM
Reserved
Aug 13, 2025, 12:00 AM
Status
Analyzed
Published
May 8, 2026, 7:16 AM
Modified
Oct 15, 2026, 7:10 PM