CVE
Dinky server-side request forgery and file read in testConnect
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Dinky version 1.2.5 or earlier
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Dinky, from DataLinkDC, has a missing authorization flaw in its testConnect endpoint that lets any logged-in user make the server open arbitrary database connections. An attacker reached over the network with a low-privilege account can use this to probe internal hosts and ports, or to read files from the Dinky host by pointing a MySQL connection at a malicious server.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Dinky through 1.2.5 contains a missing authorization vulnerability in DataSourceController.testConnect that allows any authenticated user to open arbitrary JDBC connections by supplying caller-controlled connection settings. Attackers can probe internal hosts and ports via returned driver errors, or supply a MySQL JDBC URL enabling local-infile against a malicious server to read files from the Dinky host.
Who should check
Teams running DataLinkDC Dinky v1.2.5 and earlier, the real-time data development platform, with authenticated user accounts.
“v1.2.5 and earlier”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Dinky version 1.2.5 or earlierApply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129865 (Dinky through 1.2.5 SSRF and File Read via testConnect Endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129865 (entry last updated 2026-11-16):
Affected:
- DataLinkDC Dinky: through 1.2.5
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Dinky version 1.2.5 or earlier (source: https://hackmd.io/@hieund/cve-2026-129865-129866-dinky-datasource-testconnect-missing-authz-jdbc-ssrf-file-read)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129865 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129865 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DataLinkDC/dinky/pull/4621
- https://github.com/DataLinkDC/dinky/commit/856d9df7e0e4ddc394f16b4f33c7574ef1e9f4e6
- https://github.com/DataLinkDC/dinky/commit/a6432b189b28c6b83e237f66553305a236109cb0
- https://github.com/DataLinkDC/dinky/blob/v1.2.5/dinky-admin/src/main/java/org/dinky/controller/DataSourceController.java#L189-L207
- https://github.com/DataLinkDC/dinky/blob/v1.2.5/dinky-metadata/dinky-metadata-base/src/main/java/org/dinky/metadata/driver/AbstractJdbcDriver.java#L88-L103
- https://hackmd.io/@hieund/dinky-datasource-testconnect-missing-authz-jdbc-ssrf-file-read
- https://www.vulncheck.com/advisories/dinky-through-1.2.5-ssrf-and-file-read-via-testconnect-endpoint
- https://hackmd.io/@hieund/cve-2026-129865-129866-dinky-datasource-testconnect-missing-authz-jdbc-ssrf-file-read
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129865
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129865"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- DataLinkDC Dinky
through 1.2.5
Evidence 9
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 7
- Patch
- Patch
- Patch
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129865
Is CVE-2026-129865 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
What does this mean?
An authenticated user can make the Dinky server open JDBC connections to arbitrary hosts and ports (SSRF) and observe driver errors to probe internal services. With the MySQL type and a malicious JDBC URL, arbitrary files can be read from the Dinky host through the MySQL driver's local-infile behavior.Source: hackmd.io
Which versions are affected by CVE-2026-129865?
Dinky: through 1.2.5.Source: cve.now feed data
Am I affected, and how do I check?
Dinky version 1.2.5 and earlier is affected, and the issue is in the testConnect endpoint. To check, compare the Dinky version in use against 1.2.5.Source: hackmd.io
How do I fix CVE-2026-129865?
The checked facts name no fixed version, patch ids, or workaround. Check the vendor's advisory for a fixed release before relying on any upgrade target.Source: hackmd.io