CVE-2026-46000

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets

The security operations that verify the RESPONSE packets decrypt bits of it in place - however, the sk_buff may be shared with a packet sniffer, which would lead to the sniffer seeing an apparently corrupt packet (actually decrypted).

Fix this by handing a copy of the packet off to the specific security handler if the packet was cloned.

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

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98a2046d155f73f6cf5d2c493c5e09b4963e2e12
generic

rxrpc: Fix conn-level packet handling to unshare RESPONSE packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24481a7f573305706054c59e275371f8d0fe919f

Vendor Advisories for CVE-2026-46000(2)

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

Patch Availability(11)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 5× in last 7d / 70× 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 211 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46000?
CVE-2026-46000 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix conn-level packet handling to unshare RESPONSE packets The security operations that verify the RESPONSE packets decrypt bits of it in place - however, the sk_buff may be shared with a packet sniffer, which would lead to…
When was CVE-2026-46000 disclosed?
CVE-2026-46000 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46000 actively exploited?
CVE-2026-46000 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46000?
CVE-2026-46000 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46000, 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-46000

Explore →

Is Your Infrastructure Affected by CVE-2026-46000?

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