CVE-2026-48764

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-37830 (ENISA EUVD)Source: ENISA EUVD

8.2EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

TypeBot is a chatbot builder tool. In versions prior to 3.17.2, SSRF validation is implemented by resolving a hostname once and checking whether the resolved IP belongs to a forbidden range allowing for DNS rebinding bypass. The root cause is a time-of-check to time-of-use gap in the SSRF guard. The validator resolves the hostname and approves it, but the later request path performs a fresh resolution and connects to whatever IP the hostname maps to at that moment. The actual outbound request is then performed later using the original hostname, without pinning the validated IP to the network connection. An attacker who can supply a URL to a public bot that performs a server-side HTTP Request block or server-side script fetch can use DNS rebinding to pass the initial validation and still force the server to connect to a private or metadata address during the real request. This enables server-side access to private network services, cloud metadata endpoints, and other internal HTTP targets that the validator was intended to block. The exact downstream impact depends on the reachable internal services. Concrete consequences include metadata disclosure, access to internal admin panels, credential theft from metadata services, and further compromise through internal-only HTTP interfaces. This issue has been fixed in version 3.17.2.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.3%
EPSS %ILE
26th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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: 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 public PoC (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.

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

June 18, 2026

Last Modified

October 25, 2026

Advisory Details (3)

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

SSRF in HTTP request and script fetch flows via DNS rebinding bypass · Advisory · baptisteArno/typebot.io · GitHub

https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-hgqq-whf5-mrrf
GitHub release Patch Available

v3.17.2

Patch available: baptisteArno/typebot.io v3.17.2

https://github.com/baptisteArno/typebot.io/releases/tag/v3.17.2
GitHub commit Patch Available

commit f56c3c3f771d (baptisteArno/typebot.io)

Patch available: baptisteArno/typebot.io v3.17.2 (contains commit f56c3c3f771d)

https://github.com/baptisteArno/typebot.io/commit/f56c3c3f771df13a8c11e88f500dfdd78981bed1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 100 of 168 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. None are among the latest 100 rows. The 68 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48764?
CVE-2026-48764 is a high-severity vulnerability; its CVE record was published on June 18, 2026. TypeBot is a chatbot builder tool. In versions prior to 3.17.2, SSRF validation is implemented by resolving a hostname once and checking whether the resolved IP belongs to a forbidden range allowing for DNS rebinding bypass. The root cause is a time-of-check to time-of-use gap in the SSRF guard.…
When was the CVE record for CVE-2026-48764 published?
The CVE record for CVE-2026-48764 was published on June 18, 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-48764 actively exploited?
CVE-2026-48764 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48764?
CVE-2026-48764 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48764?
A fix for CVE-2026-48764 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48764

Explore →

Is Your Infrastructure Affected by CVE-2026-48764?

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