CVE-2026-98127

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-09-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-86958 (ENISA EUVD) · GHSA-5w48-8xg9-2grf (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
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.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

smb/client: validate new EOF for insert range

smb3_insert_range() does not check if the new file size (i_size + len) is valid. This allows FALLOC_FL_INSERT_RANGE to bypass RLIMIT_FSIZE, exceed s_maxbytes, or produce a size outside the loff_t range.

Use check_add_overflow() to calculate the new EOF. Validate it with inode_newsize_ok() before modifying the file.

Reproducer, using a file on a CIFS mount:

bash -c ' FILE=/mnt/cifs/repro

trap "" SIGXFSZ ulimit -f 3072 # RLIMIT_FSIZE = 3 MiB

# A regular write is stopped at 3 MiB. dd if=/dev/zero of="$FILE" bs=1M count=4 status=none stat -c "size after write: %s" "$FILE"

# Insert 2 MiB into a 2 MiB file. truncate -s 2M "$FILE" fallocate -i -o 0 -l 2M "$FILE" stat -c "size after insert: %s" "$FILE" '

Before this change, the regular write stops at the 3 MiB limit, but insert range grows the file to 4 MiB:

dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 size after insert: 4194304

After this change, insert range also fails at the limit and leaves the 2 MiB file unchanged:

dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 fallocate: fallocate failed: File too large size after insert: 2097152

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
2nd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-18). 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; Track* at high (mission-essential systems).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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 25, 2026

Last Modified

October 22, 2026

Advisory Details (5)

Auto-updated Oct 22, 2026
Patch available.
Web page

smb/client: validate new EOF for insert range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8cbfe3a3fcee7d991fd223f660f3e5df13221cf
Web page

smb/client: validate new EOF for insert range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc7602b9082ef195d913c4c16fa9853dd262333e
Web page

smb/client: validate new EOF for insert range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b7f2e33d9f5db7b8e6e5e0a5a93d0c5e31870356
Web page

smb/client: validate new EOF for insert range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c2c69045aa76ccaa7f16f1478eb312130ce4951
Web page

smb/client: validate new EOF for insert range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1519dc88c87f5346dae0464d7d6da1b6bf1f6e8e

Vendor Advisories for CVE-2026-98127(2)

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

Patch Availability(15)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (368 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

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. 1 repeat row among the latest 95 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-11-19 00:48 UTCEchelonGraph re-scored
  5. 2026-11-19 00:48 UTCVendor advisory
  6. 2026-11-19 00:48 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf · GitHub severity MODERATE · GitHub CVSS 5.5
  7. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-30 02:55 UTCOSV refresh
  25. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 69 more
  1. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-25 13:47 UTCEchelonGraph re-scored
  5. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-22 16:08 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
  9. 2026-10-22 16:08 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  10. 2026-10-22 16:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  11. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-21 14:31 UTCVendor advisory
  13. 2026-10-21 14:31 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  14. 2026-10-21 14:27 UTCNVD update
  15. 2026-10-21 13:10 UTCEchelonGraph re-scored
  16. 2026-10-21 13:10 UTCVendor advisory
  17. 2026-10-21 13:10 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  18. 2026-10-21 13:09 UTCMITRE cvelistV5
  19. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-19 10:36 UTCVendor advisory
  22. 2026-10-19 10:36 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  23. 2026-10-19 10:25 UTCNVD update
  24. 2026-10-19 09:51 UTCEchelonGraph re-scored
  25. 2026-10-19 09:51 UTCVendor advisory
  26. 2026-10-19 09:51 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  27. 2026-10-19 09:39 UTCMITRE cvelistV5
  28. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-10-18 02:56 UTCEchelonGraph re-scored
  30. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-10-12 14:38 UTCEchelonGraph re-scored
  37. 2026-10-11 19:10 UTCEchelonGraph re-scored
  38. 2026-10-11 16:25 UTCEchelonGraph re-scored
  39. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-10-11 13:37 UTCEchelonGraph re-scored
  41. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-10-09 13:37 UTCVendor advisory
  44. 2026-10-09 13:37 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  45. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-10-06 13:55 UTCVendor advisory
  49. 2026-10-06 13:55 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  50. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  53. 2026-10-03 14:14 UTCVendor advisory
  54. 2026-10-03 14:14 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  55. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-09-30 14:33 UTCEchelonGraph re-scored
  59. 2026-09-30 14:33 UTCVendor advisory
  60. 2026-09-30 14:33 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  61. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-09-28 11:12 UTCEchelonGraph re-scored
  63. 2026-09-28 11:12 UTCVendor advisory
  64. 2026-09-28 11:12 UTCGHSA enrichmentGHSA-5w48-8xg9-2grf
  65. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  66. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-09-25 11:30 UTCNVD update
  68. 2026-09-25 10:48 UTCEchelonGraph re-scored
  69. 2026-09-25 10:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98127?
CVE-2026-98127 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for insert range smb3_insert_range() does not check if the new file size (i_size + len) is valid. This allows FALLOC_FL_INSERT_RANGE to bypass RLIMIT_FSIZE, exceed s_maxbytes, or produce a size outside…
When was the CVE record for CVE-2026-98127 published?
The CVE record for CVE-2026-98127 was published on September 25, 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-98127 actively exploited?
CVE-2026-98127 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98127?
CVE-2026-98127 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-98127?
A fix for CVE-2026-98127 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98127 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-98127

Explore →

Is Your Infrastructure Affected by CVE-2026-98127?

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