CVE-2026-45843

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: 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:

slip: bound decode() reads against the compressed packet length

slhc_uncompress() parses a VJ-compressed TCP header by advancing a pointer through the packet via decode() and pull16(). Neither helper bounds-checks against isize, and decode() masks its return with & 0xffff so it can never return the -1 that callers test for -- those error paths are dead code.

A short compressed frame whose change byte requests optional fields lets decode() read past the end of the packet. The over-read bytes are folded into the cached cstate and reflected into subsequent reconstructed packets.

Make decode() and pull16() take the packet end pointer and return -1 when exhausted. Add a bounds check before the TCP-checksum read. The existing == -1 tests now do what they were always meant to.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
19.8%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 26, 2026

Advisory Details (8)

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

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9aafba2f49e1fcccc2018816f5836a609c925879
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6268f01ae989013671b526c883e92655342c6f6f
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4cefe32639933d652614b0bd50f818f9af4af78f
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c1367a2d7aad643a6f87c6931b13cc1a25e8ca7
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37537e42e6df387398bee85cb85070cc80bb1e10
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/335957df4ed60f02a2ec0432fbedbf0cc7241d8b
generic

slip: bound decode() reads against the compressed packet length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0511ecb00e61bf28e2fec4bb41fcce385c3a3b2d

Vendor Advisories for CVE-2026-45843(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-45843?
CVE-2026-45843 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: slip: bound decode() reads against the compressed packet length slhc_uncompress() parses a VJ-compressed TCP header by advancing a pointer through the packet via decode() and pull16(). Neither helper bounds-checks against isize,…
When was CVE-2026-45843 disclosed?
CVE-2026-45843 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45843 actively exploited?
CVE-2026-45843 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45843?
CVE-2026-45843 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-45843?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45843, 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-45843

Explore →

Is Your Infrastructure Affected by CVE-2026-45843?

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