CVE-2026-31635

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 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 oversized RESPONSE authenticator length check

rxgk_verify_response() decodes auth_len from the packet and is supposed to verify that it fits in the remaining bytes. The existing check is inverted, so oversized RESPONSE authenticators are accepted and passed to rxgk_decrypt_skb(), which can later reach skb_to_sgvec() with an impossible length and hit BUG_ON(len).

Decoded from the original latest-net reproduction logs with scripts/decode_stacktrace.sh:

RIP: __skb_to_sgvec() [net/core/skbuff.c:5285 (discriminator 1)] Call Trace: skb_to_sgvec() [net/core/skbuff.c:5305] rxgk_decrypt_skb() [net/rxrpc/rxgk_common.h:81] rxgk_verify_response() [net/rxrpc/rxgk.c:1268] rxrpc_process_connection() [net/rxrpc/conn_event.c:266 net/rxrpc/conn_event.c:364 net/rxrpc/conn_event.c:386] process_one_work() [kernel/workqueue.c:3281] worker_thread() [kernel/workqueue.c:3353 kernel/workqueue.c:3440] kthread() [kernel/kthread.c:436] ret_from_fork() [arch/x86/kernel/process.c:164]

Reject authenticator lengths that exceed the remaining packet payload.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track*)
EG Risk 50/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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

pocs/dirtydecrypt at main · v12-security/pocs · GitHub

https://github.com/v12-security/pocs/tree/main/dirtydecrypt
generic

rxrpc: fix oversized RESPONSE authenticator length check - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: fix oversized RESPONSE authenticator length check - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: fix oversized RESPONSE authenticator length check - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-31635(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.23—osv

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 ... 6.19~rc8-1~exp1 (127 versions)6.19.13-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xFuffM3/CVE-2026-31635-DirtyDecrypt
    First seen May 21, 2026
    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-31635
    First seen May 19, 2026

    CVE-2026-31635

    Open source ↗

Frequently asked(5)

What is CVE-2026-31635?
CVE-2026-31635 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix oversized RESPONSE authenticator length check rxgkverifyresponse() decodes auth_len from the packet and is supposed to verify that it fits in the remaining bytes. The existing check is inverted, so oversized RESPONSE…
When was CVE-2026-31635 disclosed?
CVE-2026-31635 was first published in the National Vulnerability Database on April 24, 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-31635 actively exploited?
CVE-2026-31635 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.6% of all scored CVEs.
What is the CVSS score of CVE-2026-31635?
CVE-2026-31635 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31635?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31635, 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-31635

Explore →

Is Your Infrastructure Affected by CVE-2026-31635?

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

Start Free Scan →Browse All CVEs