VulnerabilityPublished 9 Nov 2026

CVE-2026-124572: DataLinkDC dinky · Path Traversal

Affects DataLinkDC dinkySource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 9 Nov 2026, 06:35 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulDB)	CVSS 4.0	5.3
CNA (VulDB)	CVSS 3.1	5.4
CNA (VulDB)	CVSS 3.0	5.4
CNA (VulDB)	CVSS 2.0	5.5

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
DataLinkDCdinky	Affected 1.2.0 – 1.2.5 6 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:datalinkdc:dinky:*:*:*:*:*:*:*:*

AI-suggested

Users should monitor the project's repository and the submitted GitHub Security Advisory for updates and apply any official fixes once released. Until then, restricting access to the upload functionality and validating file paths on the server side may reduce risk.

Description

CVE-2026-124572 is a path traversal vulnerability in the Catalogue Upload API of DataLinkDC dinky versions 1.2.0 through 1.2.5. The flaw exists in the CatalogueController.upload function, allowing remote attackers to manipulate file paths. This vulnerability has a medium severity rating with a CVSS score of 5.3. No public exploits or patches are currently documented.

Impact

Successful exploitation of this vulnerability could allow an attacker to read or write files outside the intended directory structure, potentially leading to unauthorized information disclosure or modification. However, the impact is limited as indicated by the medium CVSS score and limited confidentiality, integrity, and availability impact metrics.

Summary

This vulnerability affects the CatalogueController.upload function in the dinky-admin component of DataLinkDC dinky up to version 1.2.5. It allows remote attackers to perform path traversal attacks by manipulating file paths during the upload process. The issue could potentially allow unauthorized access to files outside the intended directory. The vulnerability was reported by a researcher who submitted a GitHub Security Advisory (GHSA) to the project's repository. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and limited impact on confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…