CVE-2026-129865

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-16. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-126455 (ENISA EUVD) · GHSA-649w-9hf5-2rqf (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 16, 2026

Advisory Details (7)

Auto-updated Nov 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
Web page

Dinky through 1.2.5 SSRF and File Read via testConnect Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dinky-through-1.2.5-ssrf-and-file-read-via-testconnect-endpoint
Web page

Dinky Registration Center missing function-level authorization: datasource testConnect enables SSRF and arbitrary file read, cluster config listing leaks to any user - HackMD

https://hackmd.io/@hieund/dinky-datasource-testconnect-missing-authz-jdbc-ssrf-file-read
Web page

dinky/dinky-metadata/dinky-metadata-base/src/main/java/org/dinky/metadata/driver/AbstractJdbcDriver.java at v1.2.5 · DataLinkDC/dinky · GitHub

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
Web page

dinky/dinky-admin/src/main/java/org/dinky/controller/DataSourceController.java at v1.2.5 · DataLinkDC/dinky · GitHub

https://github.com/DataLinkDC/dinky/blob/v1.2.5/dinky-admin/src/main/java/org/dinky/controller/DataSourceController.java#L189-L207
GitHub commit

commit a6432b189b28 (DataLinkDC/dinky)

Fix landed in DataLinkDC/dinky commit a6432b189b28 — awaiting tagged release

https://github.com/DataLinkDC/dinky/commit/a6432b189b28c6b83e237f66553305a236109cb0
GitHub commit

commit 856d9df7e0e4 (DataLinkDC/dinky)

Fix landed in DataLinkDC/dinky commit 856d9df7e0e4 — awaiting tagged release

https://github.com/DataLinkDC/dinky/commit/856d9df7e0e4ddc394f16b4f33c7574ef1e9f4e6
GitHub pull request

[Improve][admin] Refine data source connection and cluster configuration handling

Fix merged in DataLinkDC/dinky PR #4621 on 2026-11-16 — awaiting tagged release

https://github.com/DataLinkDC/dinky/pull/4621

Vendor Advisories for CVE-2026-129865(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-11-20 05:43 UTCEchelonGraph re-scored
  4. 2026-11-20 05:43 UTCGHSA enrichmentGHSA-649w-9hf5-2rqf · GitHub severity HIGH · GitHub CVSS 6.5
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-11-16 19:37 UTCEchelonGraph re-scored
  9. 2026-11-16 19:37 UTCGHSA enrichmentGHSA-649w-9hf5-2rqf · GitHub severity HIGH · GitHub CVSS 6.5
  10. 2026-11-16 16:02 UTCENISA EUVD ID recordedEUVD-2026-126455 · Source: ENISA EUVD
  11. 2026-11-16 15:29 UTCEchelonGraph re-scored
  12. 2026-11-16 14:40 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  13. 2026-11-16 14:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129865?
CVE-2026-129865 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. 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,…
When was CVE-2026-129865 made public?
CVE-2026-129865 was made public on November 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 16, 2026. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129865 actively exploited?
CVE-2026-129865 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129865?
CVE-2026-129865 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129865?
An upstream fix for CVE-2026-129865 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-129865 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129865

Explore →

Is Your Infrastructure Affected by CVE-2026-129865?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.