dbcve.org
CWE-15Weakness · CWE-15

CVE-2026-46485

HIGH · 8.2 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dashy versions prior to 4.0.8 have an authorization bypass in the OIDC authentication flow where the config-saving functionality fails to properly enforce permission checks. This allows unauthenticated users or authenticated non-admin users to write arbitrary changes to config.yaml, enabling unauthorized dashboard modification and potential service disruption.

MitigationUpgrade Dashy to version 4.0.8 or later to obtain the fixed code that properly enforces permission checks on the config-saving endpoint for OIDC deployments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dashy version
    Locate the Dashy installation and determine its version number (check package.json, docker image tag, or running service version). Compare this to version 4.0.8 - versions prior to 4.0.8 are affected.
    Affected if Installed version is earlier than 4.0.8
  2. Confirm OIDC authentication is enabled
    Review the Dashy configuration file (typically config.yaml) and verify that OIDC authentication is configured and active.
    Affected if OIDC authentication is enabled in the deployment
  3. Verify config-saving endpoint accessibility
    Identify whether the config-saving functionality endpoint is exposed and accessible via the Dashy web interface or API.
    Affected if The config-saving endpoint is accessible (no separate check required beyond confirming the feature exists in the UI/API)
  4. Test authorization on config-saving functionality
    Using a non-authenticated session or an authenticated non-admin user session, attempt to access or submit requests to the config-saving functionality.
    Affected if Unauthenticated users or non-admin users can successfully modify or save changes to config.yaml through the config-saving endpoint

A deployment is affected if Dashy version is earlier than 4.0.8, OIDC authentication is enabled, and the config-saving endpoint permits unauthorized write access to config.yaml.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Dashy to version 4.0.8 or later to obtain the fixed code that properly enforces permission checks on the config-saving endpoint for OIDC deployments.

Recommended fix High confidence

Dashy version 4.0.8

  1. 1. Back up your current Dashy configuration (config.yaml and any custom settings)
  2. 2. Ensure you have a way to restore the instance if issues occur
  3. 3. Upgrade Dashy to version 4.0.8 or later
  4. 4. Verify the upgrade was successful and OIDC authentication works correctly
  5. 5. Test that the config-saving functionality now properly enforces permissions
  6. 6. Confirm unauthorized users can no longer modify config.yaml

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46485 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data