# CVE-2026-122009: A flaw has been found in DataLinkDC Dinky up to 1.2.5.


- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-4fjq-hmwv-pfv4, GHSA-wchp-mjj9-wxqh

## What is CVE-2026-122009?

CVE-2026-122009 is a medium-severity vulnerability in DataLinkDC Dinky, published on 4 Nov 2026. 

### Official description

A flaw has been found in DataLinkDC Dinky up to 1.2.5. This vulnerability affects the function FlinkWebURITemplateProxyServlet.getNewTargetUri of the file dinky-admin/src/main/java/org/dinky/utils/FlinkWebURITemplateProxyServlet.java of the component flink_web Proxy Endpoint. This manipulation of the argument _authority causes server-side request forgery. The attack can be initiated remotely. The exploit has been published and may be used. The researcher claims to have submitted a GHSA on the repository of the project.

Weakness: CWE-918 (Server-Side Request Forgery)

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


## How do I fix CVE-2026-122009?

No fix has been published for CVE-2026-122009 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-122009 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122009 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122009 and fix it if it is affected.

What it is: CVE-2026-122009 is a medium-severity vulnerability in DataLinkDC Dinky, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122009 exists.

Affected product: DataLinkDC Dinky. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-122009/ (Markdown: https://insights.sbomify.com/CVE-2026-122009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-122009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-122009
- OSV: https://osv.dev/vulnerability/CVE-2026-122009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-122009/
Summaries are generated and may contain mistakes; the official description above is the record.