CVE-2026-43133

HIGHPre-NVD 7.97.9—
EchelonGraph scoreMEDIUM confidence

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

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

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation

Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01.

As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.

CVSS v3
7.9
EG Score
7.9(medium)
EG Risk
—
EPSS
2.8%
KEV
Not listed

Published

May 6, 2026

Last Modified

July 15, 2026

Advisory Details (7)

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

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3880e331b0b31d0d5d3702b124f6c93539cd478a
generic

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/127ccae2c185f62e6ecb4bf24f9cb307e9b9c619
generic

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10063e1251c1485034a018236080792ad083dcc5
generic

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0004ecb798b30e90d7ebfe74efae2d9423315a64

Vendor Advisories for CVE-2026-43133(1)

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 @ 5.15.202—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43133?
CVE-2026-43133 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed…
When was CVE-2026-43133 disclosed?
CVE-2026-43133 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on July 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-43133 actively exploited?
CVE-2026-43133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43133?
CVE-2026-43133 has a CVSS v3 base score of 7.9 (NVD).
How do I remediate CVE-2026-43133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43133, 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-43133

Explore →

Is Your Infrastructure Affected by CVE-2026-43133?

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

Start Free Scan →Browse All CVEs