CVE-2026-31710

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix dir separator in SMB1 UNIX mounts

When calling cifs_mount_get_tcon() with SMB1 UNIX mounts, @cifs_sb->mnt_cifs_flags needs to be read or updated only after calling reset_cifs_unix_caps(), otherwise it might end up with missing CIFS_MOUNT_POSIXACL and CIFS_MOUNT_POSIX_PATHS bits.

This fixes the wrong dir separator used in paths caused by the missing CIFS_MOUNT_POSIX_PATHS bit in cifs_sb_info::mnt_cifs_flags.

CVSS v3
EG Score
5.5(low)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 14, 2026

Advisory Details (2)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

smb: client: fix dir separator in SMB1 UNIX mounts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbbfcf35e1ee3396631f3dc6214cb626aa9814c3
generic

smb: client: fix dir separator in SMB1 UNIX mounts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4d3fc5844d685441befd0caaab648321013cdfd

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 7.0.2osv

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.

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 5× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 196 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-31710?
CVE-2026-31710 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix dir separator in SMB1 UNIX mounts When calling cifsmountget_tcon() with SMB1 UNIX mounts, @cifssb->mntcifs_flags needs to be read or updated only after calling resetcifsunix_caps(), otherwise it might end up with…
When was CVE-2026-31710 disclosed?
CVE-2026-31710 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31710 actively exploited?
CVE-2026-31710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
How do I remediate CVE-2026-31710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31710, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-31710?

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