Summary
CVE-2026-85691 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability affecting MegaParse, an open-source document parsing library (PyPI package megaparse, also distributed as the QuivrHQ/MegaParse repository) used to convert files such as PDFs into LLM-ready text. The flaw resides in the POST /v1/url API endpoint, which fetches attacker-supplied URLs server-side without any authentication or destination validation. The issue carries a CVSS v4.0 base score of 8.7 (High), reflecting network-exploitable, low-complexity access to internal services and metadata endpoints.
Technical details
- Root cause: The
/v1/urlendpoint inlibs/megaparse/src/megaparse/api/app.pyaccepts a rawurlparameter and passes it directly to an outbound request — either anhttpxGET request (for PDF content) or a Playwright-driven page load (for other content types) — with no scheme allowlist and no filtering of private, loopback, or link-local address ranges. - Trigger conditions: Any unauthenticated network client can send a POST request to
/v1/urlwith an internal or cloud-metadata address (e.g., RFC1918 ranges,127.0.0.1,169.254.169.254) as the target. - Attack vector: Network (AV:N), no privileges (PR:N) or user interaction (UI:N) required, low attack complexity (AC:L).
- Impact: The server-side response from the fetched URL is returned directly in the JSON response, allowing an attacker to read internal-only services, cloud instance metadata, and potentially exposed credentials/secrets, as well as perform internal network reconnaissance. Impact is limited to confidentiality (no integrity or availability impact reported).
Affected software
- MegaParse (PyPI package
megaparse), versions 0.0.0 through 0.0.55 (all released versions at time of disclosure)
Severity
- CVSS v4.0: 8.7 (High) —
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - CVSS v3.1: 7.5 (High) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - CWE-918: Server-Side Request Forgery (SSRF)
Mitigation and recommended actions
- Immediate: No patched release is currently available — as of the latest published MegaParse release (v0.0.55), the vulnerability remains unresolved and the tracking issue is open. Security teams should monitor the MegaParse repository for a fix and upgrade as soon as a patched version is released.
- Workarounds / network mitigations (until a fix ships):
- Do not expose the MegaParse
/v1/urlAPI endpoint directly to untrusted networks or the public internet. - Place the service behind authentication (e.g., an API gateway or reverse proxy enforcing auth) since the endpoint itself has no built-in authentication.
- Deploy egress filtering/network segmentation so the host running MegaParse cannot reach internal services, loopback addresses, link-local ranges (169.254.0.0/16), or cloud metadata endpoints.
- If feasible, disable or restrict the
/v1/urlroute until upstream validation (scheme allowlisting, private/loopback IP blocking, redirect/DNS-rebinding protection) is implemented.
- Do not expose the MegaParse

