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.3%, top 78% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
34.0%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 22, 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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbuildah-2:1.43.1-2.el9_82026-06-25redhat

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/crypto—0.52.0—

Weakness Classification(2)

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

All Vendor Advisories

(2)

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 8× in last 7d / 42× 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 125 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 22, 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 34.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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