# CVE-2026-124572: DataLinkDC dinky Catalogue Upload API CatalogueController.java CatalogueController.upload path traversal


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5952-4gv2-m5gj, GHSA-vqj5-2vxg-f4mq

## What is CVE-2026-124572?

CVE-2026-124572 is a medium-severity vulnerability in DataLinkDC dinky, published on 9 Nov 2026. 

### Official description

A vulnerability has been found in DataLinkDC dinky up to 1.2.5. Affected by this issue is the function CatalogueController.upload of the file dinky-admin/src/main/java/org/dinky/controller/CatalogueController.java of the component Catalogue Upload API. The manipulation leads to path traversal. The attack is possible to be carried out remotely. The researcher claims to have submitted a GHSA on the repository of the project.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-124572?


## How do I fix CVE-2026-124572?

No fix has been published for CVE-2026-124572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124572 being exploited?

There is no known exploitation of CVE-2026-124572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124572 and fix it if it is affected.

What it is: CVE-2026-124572 is a medium-severity vulnerability in DataLinkDC dinky, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124572 in the wild and no public exploit code.

Affected product: DataLinkDC dinky. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124572/ (Markdown: https://insights.sbomify.com/CVE-2026-124572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124572
- OSV: https://osv.dev/vulnerability/CVE-2026-124572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124572/
Summaries are generated and may contain mistakes; the official description above is the record.