OpenClaw is a personal AI assistant. Versions 2026.2.13 and below allow the optional @openclaw/voice-call plugin Telnyx webhook handler to accept unsigned inbound webhook requests when telnyx.publicKey is not configured, enabling unauthenticated callers to forge Telnyx events. Telnyx webhooks are expected to be authenticated via Ed25519 signature verification. In affected versions, TelnyxProvider.verifyWebhook() could effectively fail open when no Telnyx public key was configured, allowing arbitrary HTTP POST requests to the voice-call webhook endpoint to be treated as legitimate Telnyx events. This only impacts deployments where the Voice Call plugin is installed, enabled, and the webhook endpoint is reachable from the attacker (for example, publicly exposed via a tunnel/proxy). The issue has been fixed in version 2026.2.14.
CVE-2026-26319
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/openclaw/openclaw/commit/29b587e73cbdc941caec573facd16e87d52f007b
- security-advisories@githubhttps://github.com/openclaw/openclaw/commit/f47584fec86d6d73f2d483043a2ad0e7e3c50411
- security-advisories@githubhttps://github.com/openclaw/openclaw/releases/tag/v2026.2.14
- security-advisories@githubhttps://github.com/openclaw/openclaw/security/advisories/GHSA-4hg8-92x6-h2f3
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEG score recompute
- 2026-07-27 13:55 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS p91CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS p97CRITICAL
- CVE-2007-0956EG 10.0EPSS p98HIGH
- CVE-2017-12822EG 9.9CRITICAL
- CVE-2016-8355EG 9.9CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-26319?
When was CVE-2026-26319 disclosed?
Is CVE-2026-26319 actively exploited?
What is the CVSS score of CVE-2026-26319?
How do I remediate CVE-2026-26319?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26319
Is Your Infrastructure Affected by CVE-2026-26319?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.