Skip to main content
← Vulnerabilities

DataLinkDC Dinky Catalogue Upload CatalogueController.java file.getOriginalFilename path traversal

5.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
0.45% · 39th percentile
13/100 · provisional
None on Exploit-DB, Metasploit or GitHub

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.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original 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.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • DataLinkDC Dinky

    1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5

Evidence 6

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Advisory
  6. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-124326

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: cve.now feed data

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: cve.now feed data