CVE-2026-51894

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

GHSA-w4g6-3g8p-8mjr ↗EUVD-2026-91116 ↗

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-554, permanent identifier
17d 10h 03msince last run
1h 20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+84h36m
0
+2h
+4h
+6h
+8h
+10h

description

ragflow 0.24.0 is affected by an incorrect access-control issue in the run_mindmap path. An attacker who can reach this path may access data associated with a caller-selected object or tenant identifier when ownership, tenant, workspace, or membership checks are not enforced.

mitigation

Restrict access to the run_mindmap path to trusted users and enforce server-side ownership, tenant, workspace, or membership authorization before data access. No fixed version is identified in the available evidence.

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.16%4th percentile
agent run time
1h 20m
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-51894

{
  "etk_id": "ETK-2026-554",
  "cve_id": "CVE-2026-51894",
  "display_id": "CVE-2026-51894",
  "ghsa_id": "GHSA-w4g6-3g8p-8mjr",
  "euvd_id": "EUVD-2026-91116",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Incorrect access control in ragflow run_mindmap",
  "summary": "ragflow 0.24.0 is affected by an incorrect access-control issue in the run_mindmap path. An attacker who can reach this path may access data associated with a caller-selected object or tenant identifier when ownership, tenant, workspace, or membership checks are not enforced.",
  "mitigation": "Restrict access to the run_mindmap path to trusted users and enforce server-side ownership, tenant, workspace, or membership authorization before data access. No fixed version is identified in the available evidence.",
  "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": 6.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
  "epss_score": 0.0016,
  "epss_percentile": 0.0471,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 79.63409128333333,
  "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-w4g6-3g8p-8mjr"
    }
  }
}

published 2026-10-04 11:16Z
last change 2026-10-21 22:02Z

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.