CVE-2026-46059

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
Trending — 4 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN

For guests with NRIPS disabled, L1 does not provide NextRIP when running an L2 with an injected soft interrupt, instead it advances the current RIP before running it. KVM uses the current RIP as the NextRIP in vmcb02 to emulate a CPU without NRIPS.

However, after L2 runs the first time, NextRIP will be updated by the CPU and/or KVM, and the current RIP is no longer the correct value to use in vmcb02. Hence, after save/restore, use the current RIP if and only if a nested run is pending, otherwise use NextRIP. Give soft_int_next_rip the same treatment, as it's the same logic, just for a narrower use case.

[sean: give soft_int_next_rip the same treatment]

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (3)

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

KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d397582f6b5e9fbcf09781c7c934b4910e94a50
generic

KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69fe1411a5ce678b4da6489b5d2282b4e1d13acf
generic

KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb

Vendor Advisories for CVE-2026-46059(2)

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

Patch Availability(4)

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.

All Vendor Advisories

(4)

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 10× in last 7d / 57× 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.

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

Frequently asked(5)

What is CVE-2026-46059?
CVE-2026-46059 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN For guests with NRIPS disabled, L1 does not provide NextRIP when running an L2 with an injected soft interrupt, instead it advances the current RIP before…
When was CVE-2026-46059 disclosed?
CVE-2026-46059 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-46059 actively exploited?
CVE-2026-46059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46059?
CVE-2026-46059 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46059, 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-46059

Explore →

Is Your Infrastructure Affected by CVE-2026-46059?

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