Security readout for executives and security teams
Plain-English summary
CVE-2026-3052 is a server-side request forgery issue in DataLinkDC dinky’s Flink Proxy Controller. An attacker with required access may cause the server to make unintended requests. This can expose internal services reachable from the dinky server. Public proof-of-concept information exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term hardening and exposure-reduction item. Prioritize if dinky is internet-facing, broadly accessible internally, or hosted near sensitive internal services.
Technical view
The vulnerability affects proxyUba in dinky-admin/src/main/java/org/dinky/controller/FlinkProxyController.java. VulDB describes remote SSRF in DataLinkDC dinky up to 1.2.5, with CVSS 6.5 v2 and CWE-918. The vector indicates network access, low complexity, and authentication required. Vendor response was reportedly absent at disclosure time.
Likely exposure
Organizations running DataLinkDC dinky versions 1.2.0 through 1.2.5 are potentially exposed, especially if the dinky admin interface or Flink proxy functionality is reachable by users beyond trusted administrators.
Exploitation context
Sources state the exploit has been publicly disclosed and could be used. The CVSS vector indicates authentication is required. No KEV listing or cited source confirms active exploitation in the wild.
Researcher notes
Evidence is primarily VulDB and a public GitHub issue. The sources identify the affected function and SSRF class but do not provide a confirmed vendor patch. Avoid assuming exploitation beyond public PoC availability unless new telemetry or KEV status emerges.
Mitigation direction
- Identify all DataLinkDC dinky deployments and their versions.
- Restrict dinky admin and Flink proxy access to trusted networks and users.
- Limit outbound network access from dinky servers to required destinations only.
- Monitor vendor and project channels for an official fix or advisory.
- Upgrade only when a vendor-supported fixed version is identified.
Validation and detection
- Confirm whether deployed dinky versions are 1.2.0 through 1.2.5.
- Review whether Flink Proxy Controller functionality is enabled and reachable.
- Check access controls for dinky admin endpoints.
- Review logs for unusual server-initiated requests to internal or metadata services.
- Verify egress filtering prevents unnecessary internal network reachability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-347410 | DataLinkDC dinky Flink Proxy Controller FlinkProxyController.java proxyUba server-side request forgeryCVE reference · vdb-entry, technical-description
- VDB-347410 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #757587 | DataLinkDC dinky <=1.2.5 Server-Side Request ForgeryCVE reference · third-party-advisory
- https://github.com/AnalogyC0de/public_exp/issues/7CVE reference · issue-tracking, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.