cve.bz

CVE-2026-46485 lissy93 dashy: Improper Access Control

8.2 highEPSS 0.4%

High (8.2) in lissy93 dashy. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-07-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-15 External Control of System or Configuration Setting
CWE-284 Improper Access Control
CWE-287 Improper Authentication
CWE-602 Client-Side Enforcement of Server-Side Security
OWASP Top 10
A01:2025 Broken Access Control, A02:2025 Security Misconfiguration, A06:2025 Insecure Design, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-46485 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46485?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46485?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46485 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
lissy93 dashy< 4.0.8

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-176 Configuration/Environment Manipulation Severity: Medium
  • CAPEC-203 Manipulate Registry Information Severity: Medium
  • CAPEC-270 Modification of Registry Run Keys Likelihood: Medium · Severity: Medium
  • CAPEC-271 Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-579 Replace Winlogon Helper DLL

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287, CWE-602 (12), CWE-284 (17).

References

Check your stackJSON