Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85691 – Unauthenticated SSRF – MegaParse ≤ 0.0.55

Be the first to know when new zero-days emerge:

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/url endpoint in libs/megaparse/src/megaparse/api/app.py accepts a raw url parameter and passes it directly to an outbound request — either an httpx GET 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/url with 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/url API 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/url route until upstream validation (scheme allowlisting, private/loopback IP blocking, redirect/DNS-rebinding protection) is implemented.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge