cve.bz

CVE-2026-124558 DataLinkDC Dinky sql-gateway Endpoint SqlGateway.java SqlGateway.onOpen server-side request forgery

5.5 mediumEPSS 0.3%

Medium (5.5) in datalinkdc dinky. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability has been found in DataLinkDC Dinky up to 1.2.5. The impacted element is the function SqlGateway.onOpen of the file SqlGateway.java of the component sql-gateway Endpoint. Such manipulation of the argument connectAddress leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The researcher claims to have submitted a GHSA on the repository of the project.

Severity

CVSS 4.0

5.5 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulDB (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-124558 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124558?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124558?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124558 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-124558

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-124558](https://cve.bz/cve/badge/CVE-2026-124558.svg)](https://cve.bz/cve/CVE-2026-124558)

HTML:

<a href="https://cve.bz/cve/CVE-2026-124558"><img src="https://cve.bz/cve/badge/CVE-2026-124558.svg" alt="CVE-2026-124558"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
DataLinkDC Dinky1.2.0
DataLinkDC Dinky1.2.1
DataLinkDC Dinky1.2.2
DataLinkDC Dinky1.2.3
DataLinkDC Dinky1.2.4
DataLinkDC Dinky1.2.5

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON