CVE-2026-51896

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

GHSA-fjwv-9m73-7c4f ↗EUVD-2026-91114 ↗

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.
Infiniflow Ragflow n/a
CWE-284 Improper Access Control
ETK-2026-558, permanent identifier
16d 16h 21msince last run
1h 17mAI 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

Infiniflow ragflow 0.25.3 has improper access control in its resume functionality. An attacker may perform unauthorized operations across sessions or privilege boundaries when they can reach an affected exposed entry point.

mitigation

Restrict access to affected ragflow entry points to trusted, authenticated users and isolate them from untrusted networks. No fixed version or vendor-supplied workaround 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.
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
1h 17m
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-51896

{
  "etk_id": "ETK-2026-558",
  "cve_id": "CVE-2026-51896",
  "display_id": "CVE-2026-51896",
  "ghsa_id": "GHSA-fjwv-9m73-7c4f",
  "euvd_id": "EUVD-2026-91114",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper access control in ragflow resume functionality",
  "summary": "Infiniflow ragflow 0.25.3 has improper access control in its resume functionality. An attacker may perform unauthorized operations across sessions or privilege boundaries when they can reach an affected exposed entry point.",
  "mitigation": "Restrict access to affected ragflow entry points to trusted, authenticated users and isolate them from untrusted networks. No fixed version or vendor-supplied workaround is identified in the available evidence.",
  "vendor": "Infiniflow",
  "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.0726,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 77.0293159,
  "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-fjwv-9m73-7c4f"
    }
  }
}

published 2026-10-04 13:28Z
last change 2026-10-21 07:03Z

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.