CVE-2026-51893

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

GHSA-p84p-8f64-q95f ↗EUVD-2026-91117 ↗

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.
Ragflow n/a
CWE-284 Improper Access Control
ETK-2026-559, permanent identifier
16d 19h 10msince last run
1h 12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+86h45m
0
+2h
+4h
+6h
+8h
+10h

description

RAGFlow 0.24.0 is affected by an access-control flaw in the trace_mindmap path. An external attacker may access data associated with a caller-selected object or tenant identifier when that endpoint is reachable and requests are not bound to the caller’s authorized ownership, tenant, workspace, or membership.

mitigation

Restrict external access to the trace_mindmap endpoint and enforce authorization checks that bind requested objects and tenant identifiers to the authenticated caller. No fixed version is identified in the available evidence; limit access to trusted users and networks until an upstream update 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.
contextual
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.27%17th percentile
agent run time
1h 12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 00:00Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-01 00:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-01 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-559",
  "cve_id": "CVE-2026-51893",
  "display_id": "CVE-2026-51893",
  "ghsa_id": "GHSA-p84p-8f64-q95f",
  "euvd_id": "EUVD-2026-91117",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Incorrect access control in RAGFlow trace_mindmap",
  "summary": "RAGFlow 0.24.0 is affected by an access-control flaw in the trace_mindmap path. An external attacker may access data associated with a caller-selected object or tenant identifier when that endpoint is reachable and requests are not bound to the caller’s authorized ownership, tenant, workspace, or membership.",
  "mitigation": "Restrict external access to the trace_mindmap endpoint and enforce authorization checks that bind requested objects and tenant identifiers to the authenticated caller. No fixed version is identified in the available evidence; limit access to trusted users and networks until an upstream update is available.",
  "vendor": null,
  "product": "Ragflow",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 9.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0027,
  "epss_percentile": 0.1783,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 72.36214698333333,
  "t0_at": "2026-10-01T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T00:00:00+00:00",
      "url": "https://github.com/advisories/GHSA-p84p-8f64-q95f"
    }
  }
}

published 2026-10-04 13:32Z
last change 2026-10-21 07: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.