Secuno
ENNL
Book demo

CVE-2025-55449

Astrbot hard-coded credentials

7.3 HIGHPublic exploitEPSS 0.28%
  1. Published8 May 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityLow
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected products

Astrbot3.5.15

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1088609.1
BotSharp through 5.2.0 contains an authentication bypass vulnerability that allows…
CVE-2026-945918.4
Armatura One stores database and message-broker credentials in an install configuration…
CVE-2026-828279.8
Hitachi Coding Software Suite contains a vulnerability related to Use of Hard-coded…
CVE-2026-107648.7
Information disclosure in BVMS 4.5 up to 12.3 including allows man-in-the-middle…
CVE-2026-181818.1
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote…
CVE-2026-8670810.0
ZohoCorp ManageEngine Applications Manager versions 182200 and below were vulnerable to…

Frequently asked

Is CVE-2025-55449 being actively exploited?

CVE-2025-55449 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.28%.

How severe is CVE-2025-55449?

CVE-2025-55449 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.28% probability of exploitation.

Which products are affected by CVE-2025-55449?

Affected products include Astrbot.

How do I fix CVE-2025-55449?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-55449 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.