Ech0 before 4.7.3 contains an authentication bypass vulnerability in the PUT /api/echo/like/:id endpoint that allows unauthenticated attackers to increment engagement metrics without identity verification or rate limiting. Attackers can send repeated requests to arbitrarily inflate the fav_count field for any known echo identifier, compromising the integrity of engagement metrics and social ranking systems.
CVE-2026-79668
Score 5.3 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Ech0 before 4.7.3 Unauthenticated Like Endpoint Metric Inflation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ech0-before-unauthenticated-like-endpoint-metric-inflationUnauthenticated Like Endpoint Enables Arbitrary Engagement Metric Inflation · Advisory · lin-snow/Ech0 · GitHub
https://github.com/lin-snow/Ech0/security/advisories/GHSA-rgj7-vg8v-j4wrVendor Advisories for CVE-2026-79668(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/lin-snow/ech0 | — | 1.4.8-0.20260503040728-a7e8b8e84bd1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 11:40 UTCEG score recompute
- 2026-08-29 11:39 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 13:33 UTCGHSA enrichment
- 2026-08-27 15:28 UTCEG score recompute
- 2026-08-27 15:28 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:23 UTCEG score recompute
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 16:23 UTCEG score recompute
- 2026-08-26 16:23 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 10:21 UTCEG score recompute
- 2026-08-26 10:20 UTCGHSA enrichment
- 2026-08-25 12:17 UTCEG score recompute
- 2026-08-25 11:42 UTCEG score recompute
- 2026-08-25 11:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS p90CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS p97CRITICAL
- CVE-2007-0956EG 10.0EPSS p98HIGH
- CVE-2017-12822EG 9.9CRITICAL
- CVE-2016-8355EG 9.9CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-79668?
When was CVE-2026-79668 disclosed?
Is CVE-2026-79668 actively exploited?
What is the CVSS score of CVE-2026-79668?
How do I remediate CVE-2026-79668?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79668
Is Your Infrastructure Affected by CVE-2026-79668?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.