CVE-2026-31696

NVD 0.07.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 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:

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing

In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so.

This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON().

[ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc]

Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.

CVSS v3
EG Score
7.8(medium)
EPSS
2.9%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 14, 2026

Advisory Details (5)

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4458757c020592a3094366e0fb20457383b42f92
generic

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fa36cf495b0023e8475d038535c05e4063211e1

Vendor Advisories for CVE-2026-31696(2)

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 8× in last 7d / 39× 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 168 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-31696?
CVE-2026-31696 is a publicly disclosed vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While…
When was CVE-2026-31696 disclosed?
CVE-2026-31696 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-31696 actively exploited?
CVE-2026-31696 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-31696?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31696, 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-31696

Explore →

Is Your Infrastructure Affected by CVE-2026-31696?

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