CVE-2026-46598

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
23.3%
KEV
Not listed

Published

May 22, 2026

Last Modified

May 28, 2026

Advisory Details (4)

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

GO-2026-5033 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5033
generic
https://groups.google.com/g/golang-announce/c/a082jnz-LvI
generic

x/crypto/ssh/agent: pathological inputs can lead to client panic · Issue #79596 · golang/go · GitHub

https://go.dev/issue/79596
generic
https://go.dev/cl/781360

Vendor Advisories for CVE-2026-46598(3)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—0.52.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-46598?
CVE-2026-46598 is a medium vulnerability published on May 22, 2026. For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.
When was CVE-2026-46598 disclosed?
CVE-2026-46598 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46598 actively exploited?
CVE-2026-46598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46598?
CVE-2026-46598 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-46598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46598, 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-46598

Explore →

Is Your Infrastructure Affected by CVE-2026-46598?

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

Start Free Scan →Browse All CVEs