Internal response disclosure via unvalidated Invoke URL
Published Aug 18, 2026 · Updated Aug 18, 2026
Server-side request forgery in the agent Invoke component in InfiniFlow RAGFlow before 0.26.3 allows remote authenticated users to read internal HTTP responses. In agent/component/invoke.py, _build_url resolves canvas and runtime template variables into a destination URL and _invoke sends it through requests without calling the shared assert_url_is_safe guard or pinning the resolved address before returning response text as component output. Any user who can create or trigger an agent can target loopback, link-local, RFC 1918, or cloud metadata endpoints, and an agent that interpolates {sys.query} into the URL lets any chat user who can run that agent choose the destination.
Summary
What happened
Server-side request forgery in the agent Invoke component in InfiniFlow RAGFlow before 0.26.3 allows remote authenticated users to read internal HTTP responses. In agent/component/invoke.py, _build_url resolves canvas and runtime template variables into a destination URL and _invoke sends it through requests without calling the shared assert_url_is_safe guard or pinning the resolved address before returning response text as component output. Any user who can create or trigger an agent can target loopback, link-local, RFC 1918, or cloud metadata endpoints, and an agent that interpolates {sys.query} into the URL lets any chat user who can run that agent choose the destination.
The record
- CVE
- CVE-2026-75898
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- InfiniFlow
- Product
- RAGFlow
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.26.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PoC script in infiniflow/ragflow issue #18280proof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo