CVE-2026-10031

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-31) is not newer than that change (2026-10-01), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

SFTPGo prior to 2.7.4 contains a permission bypass vulnerability that allows authenticated users to circumvent per-directory access controls by creating symbolic links in a permitted directory that point to files in directories where download, upload, or overwrite permissions are denied. Attackers can exploit the create_symlinks permission combined with read and write access in one directory to read or modify files in restricted directories, as operations are authorized against the link's directory permissions rather than the dereferenced target's directory permissions.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

July 30, 2026

Last Modified

October 1, 2026

Advisory Details (4)

Auto-updated Jul 30, 2026
Patch available. Sources: github_release, github.
Web page

SFTPGo 2.7.4 Permission Bypass via Symbolic Link Creation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sftpgo-permission-bypass-via-symbolic-link-creation
GitHub advisoryMentions a patch (unverified)

Folder Permission Bypass via Symlink Dereference · Advisory · drakkan/sftpgo · GitHub

https://github.com/drakkan/sftpgo/security/advisories/GHSA-fj9v-mxr3-w75w
GitHub release Patch Available

v2.7.4

Patch available: drakkan/sftpgo v2.7.4

https://github.com/drakkan/sftpgo/releases/tag/v2.7.4
Web page

GitHub - drakkan/sftpgo: Full-featured and highly configurable SFTP, HTTP/S, FTP/S and WebDAV server - S3, Google Cloud Storage, Azure Blob · GitHub

https://github.com/drakkan/sftpgo

Vendor Advisories for CVE-2026-10031(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10031?
CVE-2026-10031 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. SFTPGo prior to 2.7.4 contains a permission bypass vulnerability that allows authenticated users to circumvent per-directory access controls by creating symbolic links in a permitted directory that point to files in directories where download, upload, or overwrite permissions are denied. Attackers…
When was CVE-2026-10031 made public?
CVE-2026-10031 was made public on July 30, 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 30, 2026. EchelonGraph's copy of the record carries a last-modified date of October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-10031 actively exploited?
CVE-2026-10031 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10031?
CVE-2026-10031 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10031?
A fix for CVE-2026-10031 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-10031 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-10031?

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

Book a Demo →Browse All CVEs