CVE-2026-48716

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th 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-37933 (ENISA EUVD)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan mitigationRemediate 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.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

nanobot is a personal AI assistant. In versions 0.1.5.post3 and prior, the WhatsApp bridge in bridge/src/whatsapp.ts constructs a filesystem path using the fileName field from an incoming WhatsApp document message without sanitization. The WhatsApp bridge downloads media attachments and writes them to disk using a filename derived from the sender's message via documentMessage.fileName, which is concatenated with a prefix and its raw value is passed directly to path.join(mediaDir, outFilename). Node.js path.join resolves .. components, allowing an attacker to escape the intended media/ directory by sending a document with a crafted fileName such as ../../../.ssh/authorized_keys. Because the attacker also controls the file content (the downloaded buffer), this is a write-anywhere primitive — both path and content are attacker-controlled. A fix for this issue is planned for version 0.1.5.post4.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.3%
EPSS %ILE
25th
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.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 (1)

Auto-updated Jun 18, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Path traversal via unsanitized WhatsApp document fileName enables arbitrary file write · Advisory · HKUDS/nanobot · GitHub

https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 150 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 50 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48716?
CVE-2026-48716 is a high-severity vulnerability; its CVE record was published on June 18, 2026. nanobot is a personal AI assistant. In versions 0.1.5.post3 and prior, the WhatsApp bridge in bridge/src/whatsapp.ts constructs a filesystem path using the fileName field from an incoming WhatsApp document message without sanitization. The WhatsApp bridge downloads media attachments and writes them…
When was the CVE record for CVE-2026-48716 published?
The CVE record for CVE-2026-48716 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-48716 actively exploited?
CVE-2026-48716 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48716?
CVE-2026-48716 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48716?
No fix for CVE-2026-48716 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48716?

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