CVE-2026-79314

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-22. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

A horizontal privilege escalation vulnerability exists in x-ui 0.3.2. An authenticated user can modify the inbound proxy configurations of other users, including remark, port, protocol, settings, enabled state, expiry time and traffic quota, by submitting a request referencing the target resource identifier. The update path fails to verify that the target resource belongs to the requesting session user, allowing unauthorized cross-user modification of data.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

September 26, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

TraceLoom/CVEs/CVE-2026-79314.md at main · lichoin/TraceLoom · GitHub

https://github.com/lichoin/TraceLoom/blob/main/CVEs/CVE-2026-79314.md
generic

GitHub - vaxilu/x-ui: 支持多协议多用户的 xray 面板 · GitHub

https://github.com/vaxilu/x-ui

Vendor Advisories for CVE-2026-79314(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 50× 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-10-05 10:28 UTCEG score recompute
  2. 2026-10-05 10:27 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 21:55 UTCGHSA enrichment
  5. 2026-10-04 09:23 UTCGHSA enrichment
  6. 2026-10-03 20:50 UTCEG score recompute
  7. 2026-10-03 20:50 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 08:17 UTCGHSA enrichment
  10. 2026-10-02 19:41 UTCEG score recompute
  11. 2026-10-02 19:41 UTCGHSA enrichment
  12. 2026-10-02 17:57 UTCEPSS rescore
  13. 2026-10-02 07:08 UTCEG score recompute
  14. 2026-10-02 07:08 UTCGHSA enrichment
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-10-01 18:35 UTCGHSA enrichment
  17. 2026-10-01 05:57 UTCGHSA enrichment
  18. 2026-09-30 17:24 UTCEG score recompute
  19. 2026-09-30 17:24 UTCGHSA enrichment
  20. 2026-09-30 04:50 UTCGHSA enrichment
  21. 2026-09-29 16:17 UTCEG score recompute
  22. 2026-09-29 16:17 UTCGHSA enrichment
  23. 2026-09-29 15:24 UTCEPSS rescore
  24. 2026-09-29 03:44 UTCEG score recompute
  25. 2026-09-29 03:44 UTCGHSA enrichment
Show 25 more
  1. 2026-09-28 15:11 UTCEG score recompute
  2. 2026-09-28 15:11 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 02:37 UTCGHSA enrichment
  5. 2026-09-27 14:04 UTCEG score recompute
  6. 2026-09-27 14:04 UTCGHSA enrichment
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-27 01:32 UTCEG score recompute
  9. 2026-09-27 01:32 UTCGHSA enrichment
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-26 12:58 UTCEG score recompute
  12. 2026-09-26 12:58 UTCGHSA enrichment
  13. 2026-09-26 00:28 UTCEPSS rescore
  14. 2026-09-26 00:25 UTCGHSA enrichment
  15. 2026-09-25 23:30 UTCEG score recompute▲ 8.80
  16. 2026-09-25 23:29 UTCGHSA enrichment
  17. 2026-09-25 23:29 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  18. 2026-09-25 14:54 UTCEG score recompute
  19. 2026-09-25 14:54 UTCGHSA enrichment
  20. 2026-09-24 14:04 UTCEPSS rescore
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-22 20:12 UTCGHSA enrichment
  23. 2026-09-22 15:18 UTCNVD update
  24. 2026-09-22 14:50 UTCEG score recompute
  25. 2026-09-22 14:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79314?
CVE-2026-79314 is a high vulnerability published on September 22, 2026. A horizontal privilege escalation vulnerability exists in x-ui 0.3.2. An authenticated user can modify the inbound proxy configurations of other users, including remark, port, protocol, settings, enabled state, expiry time and traffic quota, by submitting a request referencing the target resource…
When was CVE-2026-79314 disclosed?
CVE-2026-79314 was first published on September 22, 2026, with the most recent update on September 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79314 actively exploited?
CVE-2026-79314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79314?
CVE-2026-79314 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79314?
No fix for CVE-2026-79314 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-79314 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-79314?

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

Book a Demo →Browse All CVEs