CVE-2026-60102

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. A secondary CVSS source baseline 8.8; 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
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Horde Virtual File System (VFS) API before 3.0.1 contains an OS command injection vulnerability in the Horde_Vfs_Smb driver where the _escapeShellCommand() method fails to sanitize command substitution sequences, allowing authenticated attackers to inject arbitrary shell commands through user-controlled filenames. Attackers can supply malicious filenames containing unescaped command substitution payloads through operations such as file upload, folder creation, rename, or deletion, which are interpolated into a double-quoted shell context and executed via proc_open() through /bin/sh -c before smbclient runs, resulting in arbitrary command execution on the underlying system.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
41
EG Risk 41/100

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 computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation3.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.3%
EPSS %ILE
88th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (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

July 8, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github_release, github_commit, github_pr.
Web page

Horde VFS < 3.0.1 OS Command Injection via Horde_Vfs_Smb Driver | Advisories | VulnCheck

https://www.vulncheck.com/advisories/horde-vfs-os-command-injection-via-horde-vfs-smb-driver
GitHub release Patch Available

3.0.1

Patch available: horde/Vfs v3.0.1

https://github.com/horde/Vfs/releases/tag/v3.0.1
GitHub pull request Patch Available

fix(vfs): quote smbclient arguments to prevent command injection (CVE-2026-60102)

Patch available: horde/Vfs v3.0.1 (PR #10 merged 2026-07-08)

https://github.com/horde/Vfs/pull/10
GitHub commit Patch Available

commit 41f74b4acfc1 (horde/Vfs)

Patch available: horde/Vfs v3.0.1 (contains commit 41f74b4acfc1)

https://github.com/horde/Vfs/commit/41f74b4acfc144e09013d04dd121e0a5da808361

Vendor Advisories for CVE-2026-60102(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
php-horde-vfs2.4.1-2, 2.4.2-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php-horde-vfs2.4.2-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-60102?
CVE-2026-60102 is a high-severity vulnerability; its CVE record was published on July 8, 2026. Horde Virtual File System (VFS) API before 3.0.1 contains an OS command injection vulnerability in the HordeVfsSmb driver where the escapeShellCommand() method fails to sanitize command substitution sequences, allowing authenticated attackers to inject arbitrary shell commands through…
When was CVE-2026-60102 made public?
CVE-2026-60102 was made public on July 8, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-60102 actively exploited?
CVE-2026-60102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60102?
CVE-2026-60102 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60102?
A fix for CVE-2026-60102 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60102 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-60102?

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