CVE-2026-59692

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-09. The CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
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: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A stack buffer overflow vulnerability was found in GStreamer's DTLS plugin. During a DTLS handshake, the peer certificate Subject Distinguished Name is printed into a fixed-size 2048-byte stack buffer without bounds checking. A remote unauthenticated attacker can send a certificate with an oversized Subject DN that exceeds the buffer, causing a stack buffer overflow and process crash, resulting in denial of service.

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.
Exploitation1.0% × 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
1.0%
EPSS %ILE
61st
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

July 9, 2026

Last Modified

September 10, 2026

Advisory Details (4)

Auto-updated Jul 9, 2026
Patch available. Sources: redhat.
Red Hat

2497344 – (CVE-2026-59692) CVE-2026-59692 gstreamer: gstreamer: DTLS certificate Subject DN stack buffer overflow in openssl_verify_callback

https://bugzilla.redhat.com/show_bug.cgi?id=2497344
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-59692

Patch Availability(11)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gst-plugins-bad1.01.18.4-3 ... 1.29.2-2 (110 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gst-plugins-bad1.01.22.0-4 ... 1.29.2-2 (97 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gst-plugins-bad1.01.26.10-1 ... 1.29.2-2 (41 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gst-plugins-bad1.01.26.10-1 ... 1.28.4-1 (30 versions)
  • every version up to 1.28.5-1: fixed in 1.28.5-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59692?
CVE-2026-59692 is a high-severity vulnerability; its CVE record was published on July 9, 2026. A stack buffer overflow vulnerability was found in GStreamer's DTLS plugin. During a DTLS handshake, the peer certificate Subject Distinguished Name is printed into a fixed-size 2048-byte stack buffer without bounds checking. A remote unauthenticated attacker can send a certificate with an…
When was CVE-2026-59692 made public?
CVE-2026-59692 was made public on July 8, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 9, 2026. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-59692 actively exploited?
CVE-2026-59692 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59692?
CVE-2026-59692 has a CVSS base score of 7.5 (the CNA's own assessment, by redhat; NVD's own analysis pending).
How do I remediate CVE-2026-59692?
A fix for CVE-2026-59692 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59692 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-59692

Explore →

Is Your Infrastructure Affected by CVE-2026-59692?

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