CVE-2026-46039

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-27. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

rxgk: Fix potential integer overflow in length check

Fix potential integer overflow in rxgk_extract_token() when checking the length of the ticket. Rather than rounding up the value to be tested (which might overflow), round down the size of the available data.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

rxgk: Fix potential integer overflow in length check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6929350080f4da292d111a3b33e53138fee51cec
generic

rxgk: Fix potential integer overflow in length check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/183d37f12d1c8ed24a5bfc7addad05510da22a94
generic

rxgk: Fix potential integer overflow in length check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43222ac484f93b3ec2d240a7575e1cedd31f5fa4

Vendor Advisories for CVE-2026-46039(1)

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

Patch Availability(15)

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 10× in last 7d / 55× 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 446 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46039?
CVE-2026-46039 is a critical vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: rxgk: Fix potential integer overflow in length check Fix potential integer overflow in rxgkextracttoken() when checking the length of the ticket. Rather than rounding up the value to be tested (which might overflow), round down the…
When was CVE-2026-46039 disclosed?
CVE-2026-46039 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46039 actively exploited?
CVE-2026-46039 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 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46039?
CVE-2026-46039 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46039, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46039?

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