CVE-2026-3051: A vulnerability has been found in DataLinkDC dinky up to 1.2.5

Q: How do I fix CVE-2026-3051?

dinky: upgrade to newer than 1.2.5. Exact commands for each OS are on this page.

Q: Is CVE-2026-3051 being exploited?

CVE-2026-3051 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-3051 affect?

CVE-2026-3051 affects dinky. Severity is medium (CVSS 6.3). A vulnerability has been found in DataLinkDC dinky up to 1.2.5. The affected element is the function getProjectDir of the file dinky-admin/src/main/java/org/dinky/utils/GitRepository.java of the component Project Name Handler. Such manipula

Q: How urgent is CVE-2026-3051?

Priority 51/100. EPSS top 6%: very likely to be exploited; Public exploit reference

This month

MEDIUM 6.3UPGRADE

CVE-2026-3051 is a medium-severity flaw (CVSS 6.3) affecting dinky. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability has been found in DataLinkDC dinky up to 1.2.5. The affected element is the function getProjectDir of the file dinky-admin/src/main/java/org/dinky/utils/GitRepository.java of the component Project Name Handler. Such manipulation of the argument projectName leads to path traversal. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclos

Why this priority

EPSS top 6%: very likely to be exploited
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	7.3% (top 6%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-02-24
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: dinky

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-24 01:16 UTCPublished CVE record published
2026-06-17 10:42 UTCUpdated Record last modified

dinky dinky UPGRADE

Affected: <= 1.2.5

Fixed in: newer than 1.2.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dinky || rpm -q dinky || dinky --version

2. UPGRADE to newer than 1.2.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dinky

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dinky

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-3051?

dinky: upgrade to newer than 1.2.5. Exact commands for each OS are on this page.

Is CVE-2026-3051 being exploited?

CVE-2026-3051 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-3051 affect?

CVE-2026-3051 affects dinky. Severity is medium (CVSS 6.3). A vulnerability has been found in DataLinkDC dinky up to 1.2.5. The affected element is the function getProjectDir of the file dinky-admin/src/main/java/org/dinky/utils/GitRepository.java of the component Project Name Handler. Such manipula

How urgent is CVE-2026-3051?

Priority 51/100. EPSS top 6%: very likely to be exploited; Public exploit reference

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-3053 HIGH 7.3 UPGRADE A vulnerability was determined in DataLinkDC dinky up to 1.2.5
CVE-2026-3052 MEDIUM 6.3 UPGRADE A vulnerability was found in DataLinkDC dinky up to 1.2.5

References

← Back to latest CVEs