# CVE-2026-124326: DataLinkDC Dinky path traversal in file upload

Source: https://junglewise.ai/threats/cve-2026-124326-a-flaw-has-been-found-in-datalinkdc-dinky-up-to-1-2-5-impacted  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-124326 · Severity: medium · CVSS 5.4 · Published 2026-11-08

Dinky is a real-time data development platform built on Apache Flink for SQL-based data processing. A path traversal vulnerability in the file upload feature allows attackers to write files outside the intended directory by manipulating the filename parameter, potentially leading to unauthorized file creation or code execution on the server.

Technologies: [DataLinkDC Dinky](https://junglewise.ai/threats/technologies/dinky). Vendors: [DataLinkDC](https://junglewise.ai/threats/vendors/datalinkdc).

## Quick answers

**Is CVE-2026-124326 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-124326 being exploited in the wild.

**How severe is CVE-2026-124326?** Medium severity, with a CVSS score of 5.4, published 8 November 2026.

**Which products and versions are affected?** DataLinkDC Dinky up to 1.2.5.

**Is there a fix for CVE-2026-124326?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-124326 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-124326?** Check whether you run DataLinkDC Dinky at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in the CatalogueController.java file within the Catalogue Upload component. The getOriginalFilename() function fails to properly validate user-supplied filename inputs, allowing path traversal sequences (such as ../) to be injected. This can be exploited remotely without authentication to write files to arbitrary locations on the system.

## Affected products

- DataLinkDC Dinky up to 1.2.5

## Timeline

- 2026-11-08: disclosed

## References

- [https://github.com/DataLinkDC/dinky/](https://github.com/DataLinkDC/dinky/)
- [https://github.com/DataLinkDC/dinky/security/advisories/GHSA-2jp7-3h24-h6r7](https://github.com/DataLinkDC/dinky/security/advisories/GHSA-2jp7-3h24-h6r7)

## Related threats

- [DataLinkDC dinky path traversal in Catalogue Upload API](https://junglewise.ai/threats/cve-2026-124572-a-vulnerability-has-been-found-in-datalinkdc-dinky-up-to-1-2-5)
- [DataLinkDC Dinky server-side request forgery in SQL Gateway endpoint](https://junglewise.ai/threats/cve-2026-124558-a-vulnerability-has-been-found-in-datalinkdc-dinky-up-to-1-2-5)
- [DataLinkDC Dinky SSRF in Flink Web proxy endpoint](https://junglewise.ai/threats/cve-2026-122009-a-flaw-has-been-found-in-datalinkdc-dinky-up-to-1-2-5-this)