CVE-2026-54401

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
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: None knownExposed: 0

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

A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) to escalate privileges within such UniFi OS devices or instances.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic
https://community.ui.com/releases/Security-Advisory-Bulletin-066-066/984eceb3-49c8-4227-942d-671c289b3afc

Vendor Advisories for CVE-2026-54401(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 12× in last 7d / 72× 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 01:18 UTCEG score recompute
  2. 2026-07-27 01:18 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 13:05 UTCEG score recompute
  5. 2026-07-26 13:05 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:19 UTCEG score recompute▲ 1.10
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 02:29 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-16 21:53 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 09:43 UTCGHSA enrichment
  20. 2026-07-15 21:32 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 09:21 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 47 more
  1. 2026-07-14 21:10 UTCGHSA enrichment
  2. 2026-07-14 08:59 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 20:48 UTCGHSA enrichment
  5. 2026-07-13 08:37 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 20:24 UTCGHSA enrichment
  9. 2026-07-12 08:13 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 20:02 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 07:51 UTCGHSA enrichment
  15. 2026-07-10 19:40 UTCGHSA enrichment
  16. 2026-07-10 07:29 UTCGHSA enrichment
  17. 2026-07-10 02:56 UTCNVD updateCVSS v3 → 8.8
  18. 2026-07-09 19:15 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 07:03 UTCGHSA enrichment
  22. 2026-07-08 18:52 UTCGHSA enrichment
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 06:41 UTCGHSA enrichment
  26. 2026-07-07 18:30 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 06:20 UTCGHSA enrichment
  30. 2026-07-06 18:06 UTCGHSA enrichment
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 05:54 UTCGHSA enrichment
  34. 2026-07-06 02:23 UTCEPSS rescore
  35. 2026-07-06 02:23 UTCEPSS rescore
  36. 2026-07-05 17:35 UTCGHSA enrichment
  37. 2026-07-05 05:22 UTCGHSA enrichment
  38. 2026-07-05 02:31 UTCEPSS rescore
  39. 2026-07-05 02:30 UTCEPSS rescore
  40. 2026-07-04 17:10 UTCGHSA enrichment
  41. 2026-07-04 06:31 UTCEPSS rescore
  42. 2026-07-04 06:31 UTCEPSS rescore
  43. 2026-07-04 04:59 UTCGHSA enrichment
  44. 2026-07-03 16:48 UTCGHSA enrichment
  45. 2026-07-03 04:35 UTCGHSA enrichment
  46. 2026-07-02 16:24 UTCEG score recompute
  47. 2026-07-02 16:24 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54401?
CVE-2026-54401 is a high vulnerability published on July 2, 2026. A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) to escalate privileges within such UniFi OS devices or instances.
When was CVE-2026-54401 disclosed?
CVE-2026-54401 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54401 actively exploited?
CVE-2026-54401 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 87.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54401?
CVE-2026-54401 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-54401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54401, 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-54401

Explore →

Is Your Infrastructure Affected by CVE-2026-54401?

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

Start Free Scan →Browse All CVEs