How severe is CVE-2026-27003?

CVE-2026-27003 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-27003 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-27003?

CVE-2026-27003 affects Openclaw. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-27003?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-27003 have an EU (EUVD) identifier?

Yes. CVE-2026-27003 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8414.

When was CVE-2026-27003 published?

CVE-2026-27003 was published on 2026-02-20 and last updated on 2026-06-17.

CVE-2026-27003

CVE-2026-27003 is a medium-severity vulnerability in Openclaw with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-522.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v4: 6.9
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-8414
Weakness: CWE-522
Affected product: Openclaw
Published: 2026-02-20
Last modified: 2026-06-17

Description

OpenClaw is a personal AI assistant. Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot<token>/...`). Prior to version 2026.2.15, OpenClaw logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles. Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access. Users should upgrade to version 2026.2.15 to obtain a fix and rotate the Telegram bot token if it may have been exposed.

Frequently asked questions

What is CVE-2026-27003?: OpenClaw is a personal AI assistant. Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot<token>/...`). Prior to version 2026.2.15, OpenClaw logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles. Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access. Users should upgrade to version 2026.2.15 to obtain a fix and rotate the Telegram bot token if it may have been exposed.
How severe is CVE-2026-27003?: CVE-2026-27003 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-27003 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-27003?: CVE-2026-27003 affects Openclaw. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-27003?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-27003 have an EU (EUVD) identifier?: Yes. CVE-2026-27003 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8414.
When was CVE-2026-27003 published?: CVE-2026-27003 was published on 2026-02-20 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*

More vulnerabilities in Openclaw

CVE-2026-41329 — Critical (CVSS 9.9): OpenClaw before 2026.3.31 contains a sandbox bypass vulnerability allowing attackers to escalate privileges via…
CVE-2026-33579 — Critical (CVSS 9.9): OpenClaw before 2026.3.28 contains a privilege escalation vulnerability in the /pair approve command path that fails to…
CVE-2026-32922 — Critical (CVSS 9.9): OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with…
CVE-2026-22172 — Critical (CVSS 9.9): OpenClaw versions prior to 2026.3.12 contain an authorization bypass vulnerability in the WebSocket connect path that…
CVE-2026-28466 — Critical (CVSS 9.9): OpenClaw versions prior to 2026.2.14 contain a vulnerability in the gateway in which it fails to sanitize internal…
CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…

All CVEs affecting Openclaw →

Other CWE-522 (Insufficiently Protected Credentials) vulnerabilities

CVE-2026-7312 — Critical (CVSS 10.0): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity version from 14.0.7700 to…
CVE-2026-29128 — Critical (CVSS 10.0): IDC SFX2100 Satellite Receiver firmware ships with multiple daemon configuration files for routing components (e.g.,…
CVE-2025-54863 — Critical (CVSS 10.0): Radiometrics VizAir is vulnerable to exposure of the system's REST API key through a publicly accessible configuration…
CVE-2024-12799 — Critical (CVSS 10.0): Insufficiently Protected Credentials vulnerability in OpenText Identity Manager Advanced Edition on Windows, Linux, 64…
CVE-2024-51545 — Critical (CVSS 10.0): Username Enumeration vulnerabilities allow access to application level username add, delete, modify and list…
CVE-2023-1778 — Critical (CVSS 10.0): This vulnerability exists in GajShield Data Security Firewall firmware versions prior to v4.28 (except v4.21) due to…

Browse all CWE-522 (Insufficiently Protected Credentials) vulnerabilities →