MegaParse 0.0.55 contains an unauthenticated server-side request forgery vulnerability in the POST /v1/url endpoint that fetches caller-supplied URLs server-side. Attackers can supply internal service URLs or metadata endpoints without authentication to read their responses directly from the JSON response.
CVE-2026-85691
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 4, 2026
Last Modified
September 10, 2026
Advisory Details (4)
Auto-updated Sep 4, 2026MegaParse 0.0.55 Server-Side Request Forgery via POST /v1/url | Advisories | VulnCheck
https://www.vulncheck.com/advisories/megaparse-0.0.55-server-side-request-forgery-via-post-v1-urlmegaparse/libs/megaparse/src/megaparse/api/app.py at megaparse-v0.0.55 · The-Vibe-Company/megaparse · GitHub
https://github.com/The-Vibe-Company/megaparse/blob/megaparse-v0.0.55/libs/megaparse/src/megaparse/api/app.pyGitHub - The-Vibe-Company/megaparse: File Parser optimised for LLM Ingestion with no loss 🧠 Parse PDFs, Docx, PPTx in a format that is ideal for LLMs. · GitHub
https://github.com/The-Vibe-Company/megaparseUnauthenticated full-read SSRF via the parse-from-URL endpoint (POST /v1/url) · Issue #259 · The-Vibe-Company/megaparse · GitHub
https://github.com/The-Vibe-Company/megaparse/issues/259Vendor Advisories for CVE-2026-85691(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 66× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 23:33 UTCEG score recompute
- 2026-09-20 23:33 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 11:16 UTCGHSA enrichment
- 2026-09-19 23:00 UTCEG score recompute
- 2026-09-19 23:00 UTCGHSA enrichment
- 2026-09-19 10:45 UTCGHSA enrichment
- 2026-09-18 22:23 UTCEG score recompute
- 2026-09-18 22:22 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 10:07 UTCGHSA enrichment
- 2026-09-17 21:51 UTCEG score recompute
- 2026-09-17 21:51 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 09:35 UTCGHSA enrichment
- 2026-09-16 21:19 UTCEG score recompute
- 2026-09-16 21:19 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 09:01 UTCEG score recompute
- 2026-09-16 09:01 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 19:43 UTCGHSA enrichment
- 2026-09-15 07:19 UTCEG score recompute
- 2026-09-15 07:19 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
Show 41 moreShow fewer
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 19:02 UTCGHSA enrichment
- 2026-09-14 06:46 UTCGHSA enrichment
- 2026-09-13 18:30 UTCEG score recompute
- 2026-09-13 18:30 UTCGHSA enrichment
- 2026-09-13 06:14 UTCGHSA enrichment
- 2026-09-12 17:58 UTCEG score recompute
- 2026-09-12 17:58 UTCGHSA enrichment
- 2026-09-12 05:42 UTCGHSA enrichment
- 2026-09-11 17:26 UTCEG score recompute
- 2026-09-11 17:26 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 04:41 UTCGHSA enrichment
- 2026-09-10 16:25 UTCEG score recompute
- 2026-09-10 16:25 UTCGHSA enrichment
- 2026-09-10 15:28 UTCEG score recompute
- 2026-09-10 15:28 UTCGHSA enrichment
- 2026-09-10 11:52 UTCEG score recompute
- 2026-09-10 11:52 UTCGHSA enrichment
- 2026-09-09 23:36 UTCGHSA enrichment
- 2026-09-09 11:20 UTCGHSA enrichment
- 2026-09-08 23:04 UTCEG score recompute
- 2026-09-08 23:04 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 05:20 UTCGHSA enrichment
- 2026-09-07 17:04 UTCEG score recompute
- 2026-09-07 17:04 UTCGHSA enrichment
- 2026-09-07 04:47 UTCGHSA enrichment
- 2026-09-06 16:32 UTCEG score recompute
- 2026-09-06 16:32 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 04:15 UTCGHSA enrichment
- 2026-09-05 15:59 UTCEG score recompute
- 2026-09-05 15:59 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 03:38 UTCEG score recompute
- 2026-09-05 03:38 UTCGHSA enrichment
- 2026-09-04 15:22 UTCEG score recompute
- 2026-09-04 14:45 UTCEG score recompute
- 2026-09-04 14:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-85691?
When was CVE-2026-85691 disclosed?
Is CVE-2026-85691 actively exploited?
What is the CVSS score of CVE-2026-85691?
How do I remediate CVE-2026-85691?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85691
Is Your Infrastructure Affected by CVE-2026-85691?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.