CVE-2026-25474

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-02-17. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-8117 (ENISA EUVD) · GHSA-mp5h-m6qj-6292 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. In deployments where the webhook endpoint is reachable by an attacker, this can allow forged Telegram updates (for example spoofing message.from.id). If an attacker can reach the webhook endpoint, they may be able to send forged updates that are processed as if they came from Telegram. Depending on enabled commands/tools and configuration, this could lead to unintended bot actions. Note: Telegram webhook mode is not enabled by default. It is enabled only when channels.telegram.webhookUrl is configured. This issue has been fixed in version 2026.2.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 19, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Telegram webhook requests may be accepted without verifying secret token when webhookSecret is missing · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-mp5h-m6qj-6292
GitHub release Patch Available

openclaw 2026.2.1

Patch available: openclaw/openclaw v2026.2.1

https://github.com/openclaw/openclaw/releases/tag/v2026.2.1
GitHub commit

commit ca92597e1f95 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit ca92597e1f95 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d
GitHub commit

commit 633fe8b9c17f (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 633fe8b9c17f — awaiting tagged release

https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09
GitHub commit

commit 5643a934799d (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 5643a934799d — awaiting tagged release

https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670
GitHub commit

commit 3cbcba10cf30 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 3cbcba10cf30 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmopenclaw @ 2026.2.1 (fixes < 2026.2.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
openclaw—
  • every version up to 2026.2.1: fixed in 2026.2.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 103 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-11-01 07:57 UTCGHSA enrichmentGHSA-mp5h-m6qj-6292 · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-01 07:57 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-30 22:51 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-25 14:40 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-24 07:52 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-18 03:52 UTCEG score recompute
  22. 2026-10-17 16:45 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 74 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-12 16:19 UTCEG score recompute
  5. 2026-10-11 20:01 UTCEG score recompute
  6. 2026-10-11 17:14 UTCEG score recompute
  7. 2026-10-11 14:46 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-09 07:25 UTCOSV refresh
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-19 14:03 UTCOSV refresh
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-08-31 17:34 UTCOSV refresh
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  52. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-14 09:41 UTCEG score recompute
  57. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-13 01:53 UTCEG score recompute
  59. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-12 02:22 UTCEG score recompute
  61. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-08-11 07:15 UTCEG score recompute
  63. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-08-09 13:59 UTCEG score recompute
  65. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  66. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-08-07 21:33 UTCEG score recompute
  68. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  69. 2026-08-06 03:30 UTCEG score recompute
  70. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  72. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  73. 2026-08-02 20:13 UTCEG score recompute
  74. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Frequently asked(5)

What is CVE-2026-25474?
CVE-2026-25474 is a high-severity vulnerability; its CVE record was published on February 19, 2026. OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. In deployments where the webhook endpoint is reachable by an…
When was the CVE record for CVE-2026-25474 published?
The CVE record for CVE-2026-25474 was published on February 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-25474 actively exploited?
CVE-2026-25474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25474?
CVE-2026-25474 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-25474?
A fix for CVE-2026-25474 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25474

Explore →

Is Your Infrastructure Affected by CVE-2026-25474?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.