CVE-2026-42508

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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: cisa-adp, epss
Trending — Patch released this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 27, 2026

Advisory Details (4)

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

GO-2026-5021 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5021
generic

x/crypto/ssh/knownhosts: failure to enforce `@revoked` status · Issue #79568 · golang/go · GitHub

https://go.dev/issue/79568

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulxd-tools (2.0.11-0ubuntu1~16.04.4+esm3) @ xenial2026-07-26ubuntu
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
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17838132502026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhem/flightctl-api-rhel10:17841965882026-07-16redhat
redhatopenshift-builds/openshift-builds-waiters-rhel9:17836121192026-07-16redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat
redhatrhem/flightctl-api-rhel9:17841267802026-07-15redhat
redhatpodman-7:5.8.2-4.el10_22026-07-09redhat
redhatpodman-6:5.8.2-4.el9_82026-07-09redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatconforma-cli-stack-v1-4-1.4.22026-07-09redhat
redhatopenshift-builds/openshift-builds-waiters-rhel9:17830578682026-07-08redhat
redhatdevworkspace/devworkspace-rhel9-operator:17824016742026-07-08redhat
redhatrhem/flightctl-api-rhel9:17835020252026-07-08redhat
redhatflightctl-0:1.0.3-1.el9em2026-07-08redhat
redhatcontainer-tools:rhel8-8100020260701102925.afee755d2026-07-06redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17816864582026-06-17redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17816864462026-06-17redhat
redhatgolang1-26-main-1.26.4-2.hum12026-06-04redhat
redhatgolang1-25-main-1.25.11-2.hum12026-06-04redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto0.52.0

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-42508?
CVE-2026-42508 is a critical vulnerability published on May 22, 2026. Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.
When was CVE-2026-42508 disclosed?
CVE-2026-42508 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42508 actively exploited?
CVE-2026-42508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.3% of all scored CVEs.
What is the CVSS score of CVE-2026-42508?
CVE-2026-42508 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-42508?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42508, 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-42508

Explore →

Is Your Infrastructure Affected by CVE-2026-42508?

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