CVE-2026-13563

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability has been found in Edimax EW-7478APC 1.04. This impacts the function formL2TPSetup of the file /goform/formL2TPSetup of the component POST Request Handler. Such manipulation of the argument L2TPUserName leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/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 computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-13563(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 75× 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.

  1. 2026-07-27 16:58 UTCEG score recompute
  2. 2026-07-27 16:57 UTCGHSA enrichment
  3. 2026-07-27 14:13 UTCEPSS rescore
  4. 2026-07-27 02:55 UTCEG score recompute
  5. 2026-07-27 02:55 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:18 UTCEG score recompute
  9. 2026-07-26 14:18 UTCGHSA enrichment
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:05 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:24 UTCEPSS rescore
  16. 2026-07-20 17:08 UTCEPSS rescore
  17. 2026-07-19 02:28 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 20:32 UTCGHSA enrichment
  20. 2026-07-16 17:02 UTCEPSS rescore
  21. 2026-07-16 07:56 UTCGHSA enrichment
  22. 2026-07-15 19:20 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 06:44 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 50 more
  1. 2026-07-14 18:03 UTCGHSA enrichment
  2. 2026-07-14 05:15 UTCGHSA enrichment
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 16:39 UTCGHSA enrichment
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-13 03:54 UTCGHSA enrichment
  7. 2026-07-12 15:17 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 02:41 UTCGHSA enrichment
  10. 2026-07-11 14:04 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 01:23 UTCGHSA enrichment
  13. 2026-07-10 12:47 UTCGHSA enrichment
  14. 2026-07-10 00:12 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 11:36 UTCGHSA enrichment
  17. 2026-07-08 22:59 UTCGHSA enrichment
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-08 10:22 UTCGHSA enrichment
  21. 2026-07-07 21:45 UTCGHSA enrichment
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 09:10 UTCGHSA enrichment
  24. 2026-07-06 20:33 UTCGHSA enrichment
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 07:56 UTCGHSA enrichment
  27. 2026-07-06 02:23 UTCEPSS rescore
  28. 2026-07-05 19:18 UTCGHSA enrichment
  29. 2026-07-05 06:42 UTCGHSA enrichment
  30. 2026-07-05 02:30 UTCEPSS rescore
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-04 18:06 UTCGHSA enrichment
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-04 05:27 UTCGHSA enrichment
  35. 2026-07-03 16:50 UTCGHSA enrichment
  36. 2026-07-03 04:14 UTCGHSA enrichment
  37. 2026-07-02 15:38 UTCGHSA enrichment
  38. 2026-07-02 03:02 UTCGHSA enrichment
  39. 2026-07-01 15:06 UTCEPSS rescore
  40. 2026-07-01 15:06 UTCEPSS rescore
  41. 2026-07-01 14:26 UTCGHSA enrichment
  42. 2026-07-01 01:51 UTCGHSA enrichment
  43. 2026-06-30 23:22 UTCEPSS rescore
  44. 2026-06-30 13:14 UTCGHSA enrichment
  45. 2026-06-30 00:38 UTCGHSA enrichment
  46. 2026-06-29 17:26 UTCNVD updateCVSS v4 → 7.4
  47. 2026-06-29 16:18 UTCMITRE cvelistV5CVSS v4 → 8.7
  48. 2026-06-29 14:04 UTCNVD updateCVSS v4 → 7.4
  49. 2026-06-29 12:02 UTCEG score recompute
  50. 2026-06-29 12:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13563?
CVE-2026-13563 is a high vulnerability published on June 29, 2026. A vulnerability has been found in Edimax EW-7478APC 1.04. This impacts the function formL2TPSetup of the file /goform/formL2TPSetup of the component POST Request Handler. Such manipulation of the argument L2TPUserName leads to stack-based buffer overflow. It is possible to launch the attack…
When was CVE-2026-13563 disclosed?
CVE-2026-13563 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13563 actively exploited?
CVE-2026-13563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.6% of all scored CVEs.
What is the CVSS score of CVE-2026-13563?
CVE-2026-13563 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-13563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13563, 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

Explore the affected products and dependency analysis for CVE-2026-13563

Explore →

Is Your Infrastructure Affected by CVE-2026-13563?

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