LiveDocs: fetch_docs/introspect fetch client-supplied URLs with no host allowlist and follow redirects
LiveDocs versions below 0.7.0 are affected through fetch_docs, introspect (openapi and graphql kinds) and resolve_source docs_url. No vendor rating is given. Fixed in 0.7.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.7.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.7.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LiveDocs, a documentation tool for AI agents, has a flaw in its fetch_docs and introspect functions that pass client-supplied URLs to the network with no host allowlist and follow redirects automatically. An attacker can reach it remotely, without logging in, and with no user action, by embedding a prompt-injection payload in fetched documentation that steers the model into requesting internal or metadata endpoints and returning the responses into the conversation, which exposes high confidentiality impact.
Read the original description
LiveDocs is a primary-source-first documentation for AI agents. Prior to version 0.7.0, fetch_docs and introspect (kinds openapi/graphql, and resolve_source's docs_url) pass a client-supplied URL straight to URLSession with no scheme or host allowlist, and redirects are followed unconditionally. A prompt-injection payload embedded in fetched documentation can steer the model to call fetch_docs against internal or metadata endpoints and stream the response back into the conversation. This issue has been patched in version 0.7.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.7.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-63651 (LiveDocs: fetch_docs/introspect fetch client-supplied URLs with no host allowlist and follow redirects), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-63651 (entry last updated 2026-11-10): Affected: - PsychQuant livedocs: fixed in 0.7.0 Fixed versions: 0.7.0. Conditions (all must be true for the bug to be hit): - Affected versions are below 0.7.0. (source: https://github.com/PsychQuant/livedocs/security/advisories/GHSA-xf4p-x7v8-3x4p) - Redirects are followed unconditionally by the HTTP client. (source: https://github.com/PsychQuant/livedocs/security/advisories/GHSA-xf4p-x7v8-3x4p) - The affected surfaces are fetch_docs, introspect (openapi/graphql kinds) and resolve_source docs_url. (source: https://github.com/PsychQuant/livedocs/security/advisories/GHSA-xf4p-x7v8-3x4p) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-63651 is not listed as of cve.now's last read. This KEV status is for CVE-2026-63651 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/PsychQuant/livedocs/security/advisories/GHSA-xf4p-x7v8-3x4p - https://github.com/PsychQuant/livedocs/releases/tag/v0.7.0 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-63651 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-63651.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- PsychQuant livedocs
fixed in 0.7.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63651
Is CVE-2026-63651 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
These tools fetch URLs supplied by the client without checking the host and follow redirects automatically. That lets the server request internal or cloud metadata endpoints and return the response into the conversation.Source: github.com
Which versions are affected by CVE-2026-63651?
livedocs: before 0.7.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions below 0.7.0 are affected, on the fetch_docs tool, the introspect tool for openapi and graphql kinds, and the docs_url field of resolve_source. To check, look at the installed LiveDocs version and whether these tools are in use.Source: github.com
How do I fix CVE-2026-63651?
Upgrade LiveDocs to 0.7.0 or later, which is the listed fixed version.Source: github.com