Skip to main content
← Vulnerabilities

DataLinkDC Dinky flink_web Proxy Endpoint FlinkWebURITemplateProxyServlet.java FlinkWebURITemplateProxyServlet.getNewTargetUri server-side…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.9MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

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.

Published
Last modified
Published
Not listed in CISA KEV
29/100 · provisional
None on Exploit-DB, Metasploit or GitHub

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.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • DataLinkDC Dinky

    1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5

Evidence 6

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Advisory
  6. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-122009

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: cve.now feed data

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: cve.now feed data