Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-46485 – Authorization Bypass – Dashy prior to 4.0.8

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-46485 is a high-severity authorization bypass vulnerability affecting Dashy (lissy93/dashy), a self-hostable personal dashboard, in all versions prior to 4.0.8. The flaw allows unauthenticated users — or non-admin authenticated users — to write arbitrary changes to the application’s main config.yaml via the /config-manager/save endpoint, completely circumventing OIDC-based access controls. The vulnerability carries a CVSS v3.1 score of 8.2 (HIGH).

Technical details

  • Root cause: The /config-manager/save endpoint fails to enforce authentication or authorization checks server-side. Rather than validating the identity and role of the requesting user, access control is applied only on the client side, allowing it to be trivially bypassed. This is classified under CWE-602 (Client-Side Enforcement of Server-Side Security), CWE-15 (External Control of System or Configuration Setting), CWE-284 (Improper Access Control), and CWE-287 (Improper Authentication).
  • Trigger conditions: The vulnerability is present in any Dashy deployment configured to use OpenID Connect (OIDC) authentication. Default installations without OIDC configured are not affected by this specific attack path.
  • Attack vector: A remote, unauthenticated attacker can send a crafted HTTP POST request with arbitrary YAML content directly to the /config-manager/save endpoint. No credentials or session tokens are required.
  • Impact: Successful exploitation allows an attacker to overwrite the entire config.yaml, including authentication provider settings and all configured service URLs. This can be used to redirect OIDC authentication flows to attacker-controlled identity providers, replace legitimate service URLs with malicious links to facilitate credential harvesting or phishing, and cause service disruption by corrupting the dashboard configuration.

Affected software

  • Dashy (lissy93/dashy) — all versions prior to 4.0.8

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade Dashy to version 4.0.8 or later, which contains the vendor-provided fix for this vulnerability.
  • If immediate patching is not possible: Restrict network-level access to the Dashy instance so that the /config-manager/save endpoint is not reachable from untrusted networks. Placing the dashboard behind a reverse proxy with enforced authentication at the network perimeter can reduce exposure while a patch is applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge