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
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:

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)
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
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(6)

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.100-1 ... 7.2~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

All Vendor Advisories

(6)

Data Freshness Timeline

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.