CVE-2026-46485

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

Dashy is a self-hostable personal dashboard. Prior to 4.0.8, Dashy deployments using OIDC can allow unauthenticated users or non-admin authenticated users to write changes to the main config.yaml through the config-saving functionality despite configured permissions, allowing unauthorized modification of dashboard configuration and potential service disruption. This issue is fixed in version 4.0.8.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
22.6%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 20, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Users can write to config despire permissions (OIDC tested) · Advisory · lissy93/dashy · GitHub

https://github.com/lissy93/dashy/security/advisories/GHSA-vjj9-fmvr-6h3p

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 9× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 18:25 UTCEG score recompute
  9. 2026-07-15 18:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-46485?
CVE-2026-46485 is a high vulnerability published on July 15, 2026. Dashy is a self-hostable personal dashboard. Prior to 4.0.8, Dashy deployments using OIDC can allow unauthenticated users or non-admin authenticated users to write changes to the main config.yaml through the config-saving functionality despite configured permissions, allowing unauthorized…
When was CVE-2026-46485 disclosed?
CVE-2026-46485 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46485 actively exploited?
CVE-2026-46485 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46485?
CVE-2026-46485 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-46485?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46485, 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-46485

Explore →

Is Your Infrastructure Affected by CVE-2026-46485?

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