CVE-2026-51895

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

GHSA-86mq-h2wm-8hx9 ↗EUVD-2026-91115 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.8dkevAttacks confirmed in the real world.
Ragflow n/a
CWE-284 Improper Access Control
ETK-2026-557, permanent identifier
17d 10h 06msince last run
56mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0dpublic poc+1.8dwaiting for further signals+3.6d
0
+1d

description

Ragflow 0.24.0 and earlier are affected by improper access control in the metadata update handler. Depending on how the affected endpoint is exposed, an attacker may perform unauthorized actions across sessions or privilege boundaries.

mitigation

Upgrade to a release newer than 0.24.0 after confirming it contains a fix. Until then, restrict access to the affected metadata update endpoint to trusted users and networks.

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.18%7th percentile
agent run time
56m
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).
+1.8d
Δ 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
  3. 2026-10-11 23:34Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-557",
  "cve_id": "CVE-2026-51895",
  "display_id": "CVE-2026-51895",
  "ghsa_id": "GHSA-86mq-h2wm-8hx9",
  "euvd_id": "EUVD-2026-91115",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper access control in Ragflow metadata updates",
  "summary": "Ragflow 0.24.0 and earlier are affected by improper access control in the metadata update handler. Depending on how the affected endpoint is exposed, an attacker may perform unauthorized actions across sessions or privilege boundaries.",
  "mitigation": "Upgrade to a release newer than 0.24.0 after confirming it contains a fix. Until then, restrict access to the affected metadata update endpoint to trusted users and networks.",
  "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:N/I:H/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.0731,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 56.1867806,
  "t0_at": "2026-10-01T00:00:00+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-02T18:56:33.394000+00:00",
      "days": 1.7892753935185186,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T00:00:00+00:00",
      "url": "https://github.com/infiniflow/ragflow/issues/15268"
    },
    "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-86mq-h2wm-8hx9"
    }
  }
}

published 2026-10-04 12:31Z
last change 2026-10-21 20:58Z

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.