CVE-2026-79662

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 8.0; 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
8.0EG
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.3%CVSS: 8.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Ech0 through 4.5.6 contains an OAuth redirect URI validation vulnerability in parseAndValidateClientRedirect (internal/service/auth/auth.go) that compares only the scheme and host of the client-supplied redirect_uri against the admin-configured allowlist, ignoring path, query, and fragment components. The redirect_uri is embedded into the signed state JWT at login time without validation. An attacker can craft a redirect_uri whose host matches an allowed origin but whose path is attacker-influenced; after the OAuth exchange the victim is redirected to that path with a one-time exchange code in the query string. If the code leaks (e.g., via Referer, analytics, or an open redirect on that host), the attacker can trade it at the public POST /api/auth/exchange endpoint for the victim's access and refresh tokens. Fixed in 4.7.3.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity80% × 45%
The EG Score, 8.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
23rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 OAuth Redirect URI Validation Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ech0-before-oauth-redirect-uri-validation-bypass
GitHub advisoryMentions a patch (unverified)

OAuth redirect URI validation ignores path component, enables exchange-code theft · Advisory · lin-snow/Ech0 · GitHub

https://github.com/lin-snow/Ech0/security/advisories/GHSA-p64j-f4x9-wq66

Vendor Advisories for CVE-2026-79662(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.20260503040728-a7e8b8e84bd1: fixed in 1.4.8-0.20260503040728-a7e8b8e84bd1
—
github.com/lin-snow/Ech0—
  • every version up to 1.4.8-0.20260503040728-a7e8b8e84bd1: fixed in 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 19× in last 7d / 101× 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 99 of 176 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 77 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.3% · 23rd percentile
  2. 2026-10-13 06:37 UTCEG score recompute
  3. 2026-10-13 06:37 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-12 14:58 UTCEG score recompute
  6. 2026-10-11 19:22 UTCEG score recompute
  7. 2026-10-11 16:38 UTCEG score recompute
  8. 2026-10-11 13:56 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-10 12:17 UTCEG score recompute
  12. 2026-10-10 12:16 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-09 04:30 UTCEG score recompute
  15. 2026-10-09 04:30 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-08 03:31 UTCEG score recompute
  18. 2026-10-08 03:30 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-07 05:19 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  21. 2026-10-06 16:09 UTCEG score recompute
  22. 2026-10-06 16:09 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-06 02:37 UTCEG score recompute
  25. 2026-10-06 02:37 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
Show 74 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-05 09:18 UTCEG score recompute
  3. 2026-10-05 09:17 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-04 19:50 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  6. 2026-10-04 05:36 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  7. 2026-10-03 16:27 UTCEG score recompute
  8. 2026-10-03 16:27 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-03 02:04 UTCEG score recompute
  11. 2026-10-03 02:04 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  12. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-02 12:53 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  14. 2026-10-01 22:42 UTCEG score recompute
  15. 2026-10-01 22:42 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-01 09:25 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  18. 2026-09-30 20:16 UTCEG score recompute
  19. 2026-09-30 20:15 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  20. 2026-09-30 06:50 UTCEG score recompute
  21. 2026-09-30 06:50 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  22. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-09-29 03:43 UTCEG score recompute
  24. 2026-09-29 03:43 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  25. 2026-09-28 14:19 UTCEG score recompute
  26. 2026-09-28 14:19 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  27. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-09-28 01:09 UTCEG score recompute
  29. 2026-09-28 01:09 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  31. 2026-09-27 11:59 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  32. 2026-09-26 22:07 UTCEG score recompute
  33. 2026-09-26 22:07 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  35. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  36. 2026-09-25 15:57 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  37. 2026-09-25 01:51 UTCEG score recompute
  38. 2026-09-25 01:51 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-24 12:40 UTCEG score recompute
  41. 2026-09-24 12:40 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  42. 2026-09-23 23:30 UTCEG score recompute
  43. 2026-09-23 23:30 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-09-23 10:20 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  46. 2026-09-22 21:09 UTCEG score recompute
  47. 2026-09-22 21:09 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  48. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-09-22 08:00 UTCEG score recompute
  50. 2026-09-22 08:00 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  51. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-09-21 18:49 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  53. 2026-09-21 05:37 UTCEG score recompute
  54. 2026-09-21 05:37 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  55. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  56. 2026-09-20 15:40 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  57. 2026-09-20 02:30 UTCEG score recompute
  58. 2026-09-20 02:30 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  59. 2026-09-19 13:18 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  60. 2026-09-19 00:08 UTCEG score recompute
  61. 2026-09-19 00:07 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  63. 2026-09-18 10:58 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  64. 2026-09-17 21:48 UTCEG score recompute
  65. 2026-09-17 21:48 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  66. 2026-09-17 08:37 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  67. 2026-09-16 19:27 UTCEG score recompute
  68. 2026-09-16 19:27 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-09-16 04:35 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  72. 2026-09-15 15:22 UTCEG score recompute
  73. 2026-09-15 15:22 UTCGHSA enrichmentGHSA-m5w8-4879-f4pc · GitHub severity HIGH · GitHub CVSS 8.0
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-79662?
CVE-2026-79662 is a high-severity vulnerability; its CVE record was published on August 25, 2026. Ech0 through 4.5.6 contains an OAuth redirect URI validation vulnerability in parseAndValidateClientRedirect (internal/service/auth/auth.go) that compares only the scheme and host of the client-supplied redirecturi against the admin-configured allowlist, ignoring path, query, and fragment…
When was CVE-2026-79662 made public?
CVE-2026-79662 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-79662 actively exploited?
CVE-2026-79662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79662?
CVE-2026-79662 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79662?
A fix for CVE-2026-79662 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79662 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-79662

Explore →

Is Your Infrastructure Affected by CVE-2026-79662?

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

Book a Demo →Browse All CVEs