CVE-2026-122009

waiting for further signalsZero needs more public information before it can validate it.

GHSA-4fjq-hmwv-pfv4 ↗EUVD-2026-117077 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
DataLinkDC Dinky 1.2.0; 1.2.1; 1.2.2; 1.2.3; 1.2.4; 1.2.5
ETK-2026-3551Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 02msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h55m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

DataLinkDC Dinky versions through 1.2.5 are affected in the flink_web proxy endpoint. A remote, unauthenticated attacker who can reach that endpoint may cause the server to make requests to attacker-influenced destinations.

mitigation

Restrict or disable access to the flink_web proxy endpoint and limit the host's outbound network access to approved destinations. Apply a vendor release newer than 1.2.5 when one is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 20:30Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 20:30Z
    ghsa: trigger signal, started the run
  2. 2026-11-04 20:30Z

this entry in the feed

GET /api/v1/feed/CVE-2026-122009

{
  "etk_id": "ETK-2026-3551",
  "cve_id": "CVE-2026-122009",
  "display_id": "CVE-2026-122009",
  "ghsa_id": "GHSA-4fjq-hmwv-pfv4",
  "euvd_id": "EUVD-2026-117077",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in Dinky flink_web proxy",
  "summary": "DataLinkDC Dinky versions through 1.2.5 are affected in the flink_web proxy endpoint. A remote, unauthenticated attacker who can reach that endpoint may cause the server to make requests to attacker-influenced destinations.",
  "mitigation": "Restrict or disable access to the flink_web proxy endpoint and limit the host's outbound network access to approved destinations. Apply a vendor release newer than 1.2.5 when one is available.",
  "vendor": "DataLinkDC",
  "product": "Dinky",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.2.0",
        "1.2.1",
        "1.2.2",
        "1.2.3",
        "1.2.4",
        "1.2.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Dinky",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.388056166666667,
  "t0_at": "2026-11-04T20:30:17.574000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T20:30:17.574000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T20:30:17.574000+00:00",
      "url": "https://github.com/advisories/GHSA-4fjq-hmwv-pfv4"
    }
  }
}

published 2026-11-04 23:10Z
last change 2026-11-05 00:05Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.