CVE-2026-105762

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

GHSA-8235-vv5j-mmvg ↗EUVD-2026-92866 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−140dkevAttacks confirmed in the real world.
langgenius dify < 1.13.0
fixed in 1.13.0
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-694, permanent identifier
15d 05h 46msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
public poc−4.6motrigger signal (cve.org) +0mowaiting for further signals+0.0mo
−4mo
−3mo
−2mo
−1mo

description

Dify releases before 1.13.0 include an unauthenticated API route that can make the server retrieve attacker-chosen network locations. A remote attacker may use it to reach internal services or cloud metadata endpoints, potentially exposing data or pivoting through the host.

mitigation

Upgrade Dify to version 1.13.0 or later.

fixed in 1.13.0

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.
0.35%26th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 23:04Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−140d
Δ 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-05-19 10:05Z
  2. 2026-10-05 23:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-694",
  "cve_id": "CVE-2026-105762",
  "display_id": "CVE-2026-105762",
  "ghsa_id": "GHSA-8235-vv5j-mmvg",
  "euvd_id": "EUVD-2026-92866",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated server-side request forgery in Dify",
  "summary": "Dify releases before 1.13.0 include an unauthenticated API route that can make the server retrieve attacker-chosen network locations. A remote attacker may use it to reach internal services or cloud metadata endpoints, potentially exposing data or pivoting through the host.",
  "mitigation": "Upgrade Dify to version 1.13.0 or later.",
  "vendor": "langgenius",
  "product": "dify",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.13.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.13.0"
      ],
      "package_name": "dify",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
  "epss_score": 0.0035,
  "epss_percentile": 0.2658,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.149222883333334,
  "t0_at": "2026-10-05T23:04:58.593000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-05-19T10:05:43+00:00",
      "days": -139.54115269675927,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T23:04:58.593000+00:00",
      "url": "https://github.com/langgenius/dify/security/advisories/GHSA-8235-vv5j-mmvg"
    },
    "trigger_signal": {
      "at": "2026-10-05T23:04:58.593000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T23:04:58.593000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105762"
    }
  }
}

published 2026-10-05 23:44Z
last change 2026-10-21 04:45Z

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.