CVE-2026-79660

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-08-25. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
5.3EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Ech0 versions before 4.7.3 expose guest commenter email addresses through public API endpoints due to improper JSON serialization tags on the Comment model. Unauthenticated attackers can harvest all commenter emails by calling the /api/comments and /api/comments/public endpoints without authentication.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.4%
EPSS %ILE
33rd
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 public PoC (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

August 25, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: github.
Web page

Ech0 before 4.7.3 Email Disclosure via Public API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ech0-before-email-disclosure-via-public-api
GitHub advisoryMentions a patch (unverified)

Comment model's Email field returned on public /api/comments endpoints · Advisory · lin-snow/Ech0 · GitHub

https://github.com/lin-snow/Ech0/security/advisories/GHSA-rj4g-rqgh-rx9h

Vendor Advisories for CVE-2026-79660(1)

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

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/lin-snow/ech0—
  • every version up to 1.4.8-0.20260503034700-cb8d7a997dd8: fixed in 1.4.8-0.20260503034700-cb8d7a997dd8
—
github.com/lin-snow/Ech0—
  • every version up to 1.4.8-0.20260503034700-cb8d7a997dd8: fixed in 1.4.8-0.20260503034700-cb8d7a997dd8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 82× 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 98 of 139 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 41 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-79660?
CVE-2026-79660 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. Ech0 versions before 4.7.3 expose guest commenter email addresses through public API endpoints due to improper JSON serialization tags on the Comment model. Unauthenticated attackers can harvest all commenter emails by calling the /api/comments and /api/comments/public endpoints without…
When was CVE-2026-79660 made public?
CVE-2026-79660 was made public on May 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-79660 actively exploited?
CVE-2026-79660 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79660?
CVE-2026-79660 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79660?
A fix for CVE-2026-79660 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79660 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-79660

Explore →

Is Your Infrastructure Affected by CVE-2026-79660?

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