{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46485 exists.","fix":"No fix has been published for CVE-2026-46485 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46485 is a high-severity missing authorization vulnerability in lissy93 dashy, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46485 and fix it if it is affected.\n\nWhat it is: CVE-2026-46485 is a high-severity missing authorization vulnerability in lissy93 dashy, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46485 exists.\n\nAffected product: lissy93 dashy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46485/ (Markdown: https://insights.sbomify.com/CVE-2026-46485/index.md)","id":"CVE-2026-46485","markdown":"https://insights.sbomify.com/CVE-2026-46485/index.md","name":"CVE-2026-46485","record":{"aliases":["GHSA-vjj9-fmvr-6h3p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Dashy dashboard","requires_auth":"none","summary":"Unauthenticated or non-admin users can modify the main configuration file in Dashy deployments using OIDC, leading to unauthorized changes and potential service disruption.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-602","name":"Client-Side Enforcement of Server-Side Security"},{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-15","name":"External Control of System or Configuration Setting"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Dash: Users can write to config despire permissions (OIDC tested)","id":"CVE-2026-46485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing","id":"CVE-2026-46486"},"packages":[],"prev":{"headline":"Headplane: Path Traversal + RBAC Bypass in renameNode allows authenticated OIDC users to expire or rename any node/user","id":"CVE-2026-46484"},"products":["dashy"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["lissy93"]},"summary":"Unauthenticated or non-admin users can modify the main configuration file in Dashy deployments using OIDC, leading to unauthorized changes and potential service disruption.","url":"https://insights.sbomify.com/CVE-2026-46485/"}