CVE-2026-39829

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

May 22, 2026

Last Modified

September 18, 2026

Advisory Details (5)

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

GO-2026-5018 - Go Packages

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

x/crypto/ssh: pathological RSA/DSA parameters may cause DoS · Issue #79565 · golang/go · GitHub

https://go.dev/issue/79565
generic
https://go.dev/cl/781661
generic
https://go.dev/cl/781641

Vendor Advisories for CVE-2026-39829(20)

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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpodman-5:5.4.0-22.el9_6.52026-09-14redhat
redhatrhosp-rhel8/osp-director-operator:17883545862026-09-09redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatrhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9:17881810542026-09-08redhat
redhatopenshift4/ose-azure-cluster-api-controllers-rhel9:17875452342026-09-02redhat
redhatopenshift4/ose-azure-cluster-api-controllers-rhel9:17877353522026-09-01redhat
redhatopenshift4/ose-azure-cluster-api-controllers-rhel9:17875558222026-09-01redhat
redhatcluster-observability-operator/cluster-observability-rhel9-operator:17875936372026-08-31redhat
redhatrhoai/odh-trainer-rhel9:17870890492026-08-27redhat
redhatoadp/oadp-velero-rhel9:17869445402026-08-25redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17867646012026-08-25redhat
redhatmulticluster-engine/cluster-api-provider-kubevirt-rhel9:17868372082026-08-25redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17869553162026-08-25redhat
redhatopenshift4/ose-azure-cluster-api-controllers-rhel9:17870377622026-08-25redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17869087772026-08-19redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatmulticluster-engine/cluster-api-provider-kubevirt-rhel9:17865491002026-08-12redhat
redhatrhacm2/volsync-rhel9:17864566582026-08-12redhat
redhatopenshift-gitops-1/argocd-rhel9:17852113462026-08-10redhat
redhatopenshift-gitops-1/argocd-rhel8:17851492602026-08-10redhat
redhatoadp/oadp-velero-rhel9:17851808782026-08-06redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat
redhatcontainer-tools:rhel8-8080020260721142025.63b345852026-08-04redhat
redhatopenshift4/ose-installer-rhel9:17851945122026-08-04redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17847387582026-07-29redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17841586792026-07-29redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-192026-07-29redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17845644382026-07-28redhat

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 rangeFixed inDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.10.0-1 ... 1:0.56.0-1 (36 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.56.0-1 (21 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.52.0-1~bpo13+1 (16 versions)1:0.52.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—0.52.0—

Weakness Classification(2)

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 20× in last 7d / 90× 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 326 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-39829?
CVE-2026-39829 is a high vulnerability published on May 22, 2026. The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public…
When was CVE-2026-39829 disclosed?
CVE-2026-39829 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39829 actively exploited?
CVE-2026-39829 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 60.4% of all scored CVEs.
What is the CVSS score of CVE-2026-39829?
CVE-2026-39829 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-39829?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39829, 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-39829

Explore →

Is Your Infrastructure Affected by CVE-2026-39829?

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

Start Free Scan →Browse All CVEs