{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3051 exists.","fix":"No fix has been published for CVE-2026-3051 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3051 is a medium-severity path traversal vulnerability in DataLinkDC dinky, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3051 and fix it if it is affected.\n\nWhat it is: CVE-2026-3051 is a medium-severity path traversal vulnerability in DataLinkDC dinky, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3051 exists.\n\nAffected product: DataLinkDC dinky. 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-3051/ (Markdown: https://insights.sbomify.com/CVE-2026-3051/index.md)","id":"CVE-2026-3051","markdown":"https://insights.sbomify.com/CVE-2026-3051/index.md","name":"CVE-2026-3051","record":{"aliases":["GHSA-f256-j3x2-h7wh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"DataLinkDC dinky","requires_auth":"low_privilege","summary":"Remote attackers can exploit a path traversal vulnerability in the getProjectDir function to read or modify arbitrary files on the server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"dinky","vendor":"dinky"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A vulnerability has been found in DataLinkDC dinky up to 1.2.5. The affected element is the function getProjectDir of the file dinky-admin/src/main/java/org/dinky/utils/GitRepository.java of the component Project Name Handler. Such manipulation of the argument projectName leads to path traversal. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","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":"DataLinkDC dinky Project Name GitRepository.java getProjectDir path traversal","id":"CVE-2026-3051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"DataLinkDC dinky Flink Proxy Controller FlinkProxyController.java proxyUba server-side request forgery","id":"CVE-2026-3052"},"packages":[],"prev":{"headline":"horilla-opensource horilla Leads global.js cross site scripting","id":"CVE-2026-3050"},"products":["dinky"],"published":"2026-02-24","related":[{"cvss_score":6.9,"headline":"DataLinkDC dinky OpenAPI Endpoint AppConfig.java addInterceptors missing authentication","id":"CVE-2026-3053","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":5.3,"headline":"DataLinkDC dinky Flink Proxy Controller FlinkProxyController.java proxyUba server-side request forgery","id":"CVE-2026-3052","kev_date_added":null,"published":"2026-02-24"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["DataLinkDC"]},"summary":"Remote attackers can exploit a path traversal vulnerability in the getProjectDir function to read or modify arbitrary files on the server.","url":"https://insights.sbomify.com/CVE-2026-3051/"}