CVE-2026-51892

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

GHSA-q37m-rx33-792r ↗EUVD-2026-91118 ↗

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-556, permanent identifier
14d 14h 40msince last run
55mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+135h06m
0
+2h
+4h
+6h
+8h
+10h

description

ragflow 0.24.0 has an authorization weakness in its document-retrieval functionality. An attacker who can reach the affected route may be able to retrieve documents outside their intended access permissions; access to that route is the documented precondition.

mitigation

Restrict access to the affected document-retrieval route to trusted, authenticated users and enforce authorization at a reverse proxy or other access-control layer. Upgrade when a vendor-fixed release is published; no fixed version is recorded in the available advisory data.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%13th percentile
agent run time
55m
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-51892

{
  "etk_id": "ETK-2026-556",
  "cve_id": "CVE-2026-51892",
  "display_id": "CVE-2026-51892",
  "ghsa_id": "GHSA-q37m-rx33-792r",
  "euvd_id": "EUVD-2026-91118",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization flaw in ragflow document retrieval",
  "summary": "ragflow 0.24.0 has an authorization weakness in its document-retrieval functionality. An attacker who can reach the affected route may be able to retrieve documents outside their intended access permissions; access to that route is the documented precondition.",
  "mitigation": "Restrict access to the affected document-retrieval route to trusted, authenticated users and enforce authorization at a reverse proxy or other access-control layer. Upgrade when a vendor-fixed release is published; no fixed version is recorded in the available advisory data.",
  "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:L/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1304,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 55.313592566666664,
  "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-q37m-rx33-792r"
    }
  }
}

published 2026-10-04 12:10Z
last change 2026-10-21 02:54Z

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.