CVE-2026-43336

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope

Since the ChaCha permutation is invertible, the local variable 'permuted_state' is sufficient to compute the original 'state', and thus the key, even after the permutation has been done.

While the kernel is quite inconsistent about zeroizing secrets on the stack (and some prominent userspace crypto libraries don't bother at all since it's not guaranteed to work anyway), the kernel does try to do it as a best practice, especially in cases involving the RNG.

Thus, explicitly zeroize 'permuted_state' before it goes out of scope.

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

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (8)

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91999af43ca2125e3b2c18fcfc02912ada02efc3
generic

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d761e5a7340c46479fb2399598f331e4fe2c633
generic

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1933249263c3a98df79992f61a566476e4163bcc
generic

lib/crypto: chacha: Zeroize permuted_state before it leaves scope - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/066c760acead1fb743bae294dbd89f479ae43b9b

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

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.

Data Freshness Timeline

(refreshed 9× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43336?
CVE-2026-43336 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: lib/crypto: chacha: Zeroize permuted_state before it leaves scope Since the ChaCha permutation is invertible, the local variable 'permuted_state' is sufficient to compute the original 'state', and thus the key, even after the…
When was CVE-2026-43336 disclosed?
CVE-2026-43336 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43336 actively exploited?
CVE-2026-43336 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 65.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43336?
CVE-2026-43336 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43336?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43336, 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-43336

Explore →

Is Your Infrastructure Affected by CVE-2026-43336?

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