{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24840 exists.","fix":"No fix has been published for CVE-2026-24840 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24840 is a high-severity vulnerability in dokploy, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24840 and fix it if it is affected.\n\nWhat it is: CVE-2026-24840 is a high-severity vulnerability in dokploy, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24840 exists.\n\nAffected product: dokploy. 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-24840/ (Markdown: https://insights.sbomify.com/CVE-2026-24840/index.md)","id":"CVE-2026-24840","markdown":"https://insights.sbomify.com/CVE-2026-24840/index.md","name":"CVE-2026-24840","record":{"aliases":["GHSA-jr65-3j3w-gjmc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Self-hosted PaaS","requires_auth":"low_privilege","summary":"Attackers can access databases in nearly all installations due to hardcoded credentials in the installation script, requiring an upgrade to Dokploy.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dokploy","vendor":"dokploy"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Dokploy is a free, self-hostable Platform as a Service (PaaS). In versions prior to 0.26.6, a hardcoded credential in the provided installation script (located at https://dokploy.com/install.sh, line 154) uses a hardcoded password when creating the database container. This means that nearly all Dokploy installations use the same database credentials and could be compromised. Version 0.26.6 contains a patch for the issue.","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":"Dokploy uses hardcoded credentials in installation script, which could result in database access","id":"CVE-2026-24840","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in dokploy","id":"CVE-2026-24841"},"packages":[],"prev":{"headline":"Dokploy has a clickjacking vulnerability - Missing X-Frame-Options and CSP frame-ancestors headers","id":"CVE-2026-24839"},"products":["dokploy"],"published":"2026-01-28","related":[{"cvss_score":9.9,"headline":"Command injection in dokploy","id":"CVE-2026-24841","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":9.4,"headline":"Dokploy's Preview Deployments are vulnerable to Remote Code Execution","id":"CVE-2025-53825","kev_date_added":null,"published":"2025-07-14"},{"cvss_score":6.3,"headline":"Dokploy allows attackers to run arbitrary OS commands on the Dokploy host.","id":"CVE-2025-53376","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":4.9,"headline":"Dokploy allows attackers to read any file that the Traefik process user can access","id":"CVE-2025-53375","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":4.7,"headline":"Dokploy has a clickjacking vulnerability - Missing X-Frame-Options and CSP frame-ancestors headers","id":"CVE-2026-24839","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":1.3,"headline":"Dokploy Improperly Discloses User Information via user.one Endpoint","id":"CVE-2025-53374","kev_date_added":null,"published":"2025-07-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-28","vendors":["Dokploy"]},"summary":"Attackers can access databases in nearly all installations due to hardcoded credentials in the installation script, requiring an upgrade to Dokploy.","url":"https://insights.sbomify.com/CVE-2026-24840/"}