{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3053 exists.","fix":"No fix has been published for CVE-2026-3053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3053 is a medium-severity missing authorization vulnerability in DataLinkDC dinky, published on 24 Feb 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-3053 and fix it if it is affected.\n\nWhat it is: CVE-2026-3053 is a medium-severity missing authorization vulnerability in DataLinkDC dinky, published on 24 Feb 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-3053 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-3053/ (Markdown: https://insights.sbomify.com/CVE-2026-3053/index.md)","id":"CVE-2026-3053","markdown":"https://insights.sbomify.com/CVE-2026-3053/index.md","name":"CVE-2026-3053","record":{"aliases":["GHSA-w3pf-j6xr-fj68"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"DataLinkDC dinky","requires_auth":"none","summary":"Remote attackers can bypass authentication on the OpenAPI endpoint due to missing interceptor configuration in DataLinkDC dinky.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"dinky","vendor":"dinky"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"A vulnerability was determined in DataLinkDC dinky up to 1.2.5. This affects the function addInterceptors of the file dinky-admin/src/main/java/org/dinky/configure/AppConfig.java of the component OpenAPI Endpoint. Executing a manipulation can lead to missing authentication. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. 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 OpenAPI Endpoint AppConfig.java addInterceptors missing authentication","id":"CVE-2026-3053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Alinto SOGo cross site scripting","id":"CVE-2026-3054"},"packages":[],"prev":{"headline":"DataLinkDC dinky Flink Proxy Controller FlinkProxyController.java proxyUba server-side request forgery","id":"CVE-2026-3052"},"products":["dinky"],"published":"2026-02-24","related":[{"cvss_score":5.3,"headline":"DataLinkDC dinky Project Name GitRepository.java getProjectDir path traversal","id":"CVE-2026-3051","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-28","vendors":["DataLinkDC"]},"summary":"Remote attackers can bypass authentication on the OpenAPI endpoint due to missing interceptor configuration in DataLinkDC dinky.","url":"https://insights.sbomify.com/CVE-2026-3053/"}