CVE-2026-98499

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-18. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-103739 (ENISA EUVD) · GHSA-vgmm-5fmr-gjgq (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce()

The 'wacom_wac_pen_serial_enforce()' function may calculate and pass an invalid offset to hid_field_extract(), resulting in memory reads at incorrect addresses -- possibly beyond the end of the report. If a field in the HID descriptor lists more usages than its Report Count actually reserves space for, the function's inner 'j' will walk past the end of the field:

for (i = 0; i < report->maxfield; i++) { for (j = 0; j < report->field[i]->maxusage; j++) { ... value = hid_field_extract(hdev, raw_data + 1, offset + j * size, size);

A descriptor listing 12288 usages against Report Count 1 has the loop extract the usage at index 12287 from bit offset 98296 -- about 12 KB past a 2-byte received report. The value is stored in wacom_wac->serial[0] and can reach userspace as an MSC_SERIAL event, making this an information disclosure.

Clamp the loop to field->report_count, the number of value slots the report holds. Value slots past the last declared usage are still scanned; they reuse that usage (HID 1.11, 6.2.2.8).

Verified on v6.12.105 with a UHID reproducer: a 2-byte report from such a descriptor trips KASAN before the patch and not after it.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 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 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
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.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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, 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

October 18, 2026

Last Modified

October 24, 2026

Advisory Details (8)

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

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51
Web page

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9aa237cf66495b2426ddde8532e9b08a0ed83aaa
Web page

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65e7c4b5366b770c60dfefac3f1d06e33a9e411e
Web page

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b09b7c84b8633cd041181616bd15bf5e73c164d
Web page

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/456afe4707e23cc114ad833197f63b52bb8fd1e7
Web page

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26471d954bbfbfb9032994f7f485802ee20e0582

Vendor Advisories for CVE-2026-98499(2)

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

Patch Availability(17)

These rows come from Ubuntu. 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 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (184 versions)
  • every version up to 7.2.9-1: fixed in 7.2.9-1
—

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-17 18:33 UTCEchelonGraph re-scored
  6. 2026-11-17 18:33 UTCVendor advisory
  7. 2026-11-17 18:33 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-11-16 15:13 UTCEchelonGraph re-scored
  11. 2026-11-16 15:13 UTCVendor advisory
  12. 2026-11-16 15:13 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-11-08 16:45 UTCEchelonGraph re-scored
  21. 2026-11-08 16:45 UTCVendor advisory
  22. 2026-11-08 16:45 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-11-08 16:26 UTCEchelonGraph re-scored
  25. 2026-11-08 16:26 UTCVendor advisory
Show 39 more
  1. 2026-11-08 16:26 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-11-01 03:19 UTCEchelonGraph re-scored
  10. 2026-11-01 03:19 UTCVendor advisory
  11. 2026-11-01 03:19 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-25 13:47 UTCEchelonGraph re-scored
  20. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-24 14:26 UTCEchelonGraph re-scored
  22. 2026-10-24 14:26 UTCVendor advisory
  23. 2026-10-24 14:26 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq
  24. 2026-10-24 14:14 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  25. 2026-10-24 14:14 UTCVendor advisory
  26. 2026-10-24 14:14 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq
  27. 2026-10-24 14:13 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  28. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-10-19 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-10-19 10:49 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq
  34. 2026-10-19 10:26 UTCNVD update
  35. 2026-10-19 10:00 UTCGHSA enrichmentGHSA-vgmm-5fmr-gjgq
  36. 2026-10-19 09:39 UTCMITRE cvelistV5
  37. 2026-10-18 16:25 UTCNVD update
  38. 2026-10-18 15:19 UTCEchelonGraph re-scored
  39. 2026-10-18 15:18 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

Frequently asked(5)

What is CVE-2026-98499?
CVE-2026-98499 is a high-severity vulnerability; its CVE record was published on October 18, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() The 'wacom_wac_pen_serial_enforce()' function may calculate and pass an invalid offset to hid_field_extract(), resulting in memory reads at incorrect addresses -- possibly…
When was the CVE record for CVE-2026-98499 published?
The CVE record for CVE-2026-98499 was published on October 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-98499 actively exploited?
CVE-2026-98499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98499?
CVE-2026-98499 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98499?
A fix for CVE-2026-98499 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98499 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-98499

Explore →

Is Your Infrastructure Affected by CVE-2026-98499?

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