---
id: "CVE-2026-122009"
kind: "vulnerability"
aliases: ["CVE-2026-122009"]
title: "Dinky: flaw in Flink web proxy allows server-side request forgery"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "dinky", "fixed": [], "affected": "<= 1.2.5", "ecosystem": "maven"}]
ecosystems: []
tags: ["dinky", "flink", "package", "self-hosted"]
not_affected_if: ["admin-not-network-reachable", "dinky-newer-than-1.2.5"]
published_at: "2026-11-04T21:18:07+00:00"
first_seen_at: "2026-11-04T21:49:18+00:00"
updated_at: "2026-11-04T21:54:23+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-122009", "first_seen_at": "2026-11-04T21:49:18+00:00"}, {"source": "analyst", "url": "https://vuldb.com/vuln/431072", "first_seen_at": "2026-11-04T21:54:23+00:00", "cites": ["https://vuldb.com/vuln/431072"]}]
exploit_sources: []
---

# Dinky: flaw in Flink web proxy allows server-side request forgery

Dinky, a Flink data platform, has a flaw in its Flink web proxy endpoint where the _authority argument is not validated. A remote attacker can make the Dinky server send requests to addresses of their choosing, which can reach internal services.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- maven:dinky affected <= 1.2.5 fixed ?

## How to check

- Check the installed Dinky version against the affected range (up to 1.2.5).
- Look for the flink_web proxy endpoint exposed on the Dinky admin server.

## Timeline

- 2026-11-04T21:49:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-122009
- 2026-11-04T21:54:23+00:00 analyst https://vuldb.com/vuln/431072 — Vendor GHSA returns 404 (not public/draft), so nothing verified. VulDB says Dinky <= 1.2.5, FlinkWebURITemplateProxyServlet.getNewTargetUri _authority SSRF, remote, exploit published (no link found). Fix unknown; auth requirement unknown (VulDB gives no privileges detail; CVSS vector says PR:N, but the sibling CVE-2026-3052 proxyUba SSRF needs login and the vendor never answered). Settle by reading GHSA once public or the dinky repo for a commit touching the servlet.

## Documents

- [advisory] Vendor advisory: github.com https://github.com/DataLinkDC/dinky/security/advisories/GHSA-wchp-mjj9-wxqh
- [describes] VulDB VDB-431072: Dinky flink_web proxy _authority SSRF https://vuldb.com/vuln/431072

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_