CVE-2026-46597

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 7, 2026
Patch available.
Web page

GO-2026-5013 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5013
Web page

x/crypto/ssh: byte arithmetic causes underflow and panic · Issue #79561 · golang/go · GitHub

https://go.dev/issue/79561

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17864865732026-08-19redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17864997782026-08-19redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17864938122026-08-18redhat
redhatopenshift4/ose-vsphere-csi-driver-rhel9:17864942642026-08-18redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17864944112026-08-18redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17865506672026-08-18redhat
redhatopenshift4/ose-vsphere-csi-driver-rhel9:17865497262026-08-18redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17866138052026-08-13redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17865483812026-08-12redhat
redhatrhacm2/volsync-rhel9:17864566582026-08-12redhat
redhatopenshift4/ose-hyperkube-rhel9:17858846882026-08-11redhat
redhatopenshift-0:4.22.0-202608010430.p2.g5f1e0e7.assembly.stream.el82026-08-11redhat
redhatoadp/oadp-velero-rhel9:17851808782026-08-06redhat
redhatrhtas/policy-controller-rhel9:17854162882026-08-06redhat
redhatrhtas/model-transparency-cli-rhel9:17854761062026-08-05redhat
redhatrhtas/rekor-monitor-rhel9:17853915022026-08-05redhat
redhatrhtas/timestamp-authority-rhel9:17853913832026-08-05redhat
redhatrhtas/model-validation-rhel9-operator:17854879362026-08-05redhat
redhatrhtas/rekor-cli-rhel9:17853915242026-08-05redhat
redhatopenshift4/ose-installer-artifacts-rhel9:17851945032026-08-04redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhtas/rekor-cli-rhel9:17839693652026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhtas/rekor-monitor-rhel9:17839685082026-07-16redhat
redhatrhtas/timestamp-authority-rhel9:17839686442026-07-16redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.10.0-1 ... 1:0.56.0-1 (36 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.56.0-1 (21 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.52.0-1~bpo13+1 (16 versions)
  • every version up to 1:0.52.0-1: fixed in 1:0.52.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/crypto—
  • every version up to 0.52.0: fixed in 0.52.0
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

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 11× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 245 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-46597?
CVE-2026-46597 is a high-severity vulnerability; its CVE record was published on May 22, 2026. An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.
When was the CVE record for CVE-2026-46597 published?
The CVE record for CVE-2026-46597 was published on May 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-46597 actively exploited?
CVE-2026-46597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46597?
CVE-2026-46597 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46597?
A fix for CVE-2026-46597 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46597 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46597

Explore →

Is Your Infrastructure Affected by CVE-2026-46597?

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