Internal response disclosure via unchecked URL fetch
Published Sep 4, 2026 · Updated Sep 10, 2026
Server-side request forgery in MegaParse 0.0.55 allows remote attackers to read internal HTTP responses via POST /v1/url. The route passes its raw URL parameter to httpx or a Playwright loader without scheme, host, or private-address validation, then returns fetched content in JSON. No authentication is required, exposing reachable internal services and metadata responses but no reported write or availability impact.
Summary
What happened
Server-side request forgery in MegaParse 0.0.55 allows remote attackers to read internal HTTP responses via POST /v1/url. The route passes its raw URL parameter to httpx or a Playwright loader without scheme, host, or private-address validation, then returns fetched content in JSON. No authentication is required, exposing reachable internal services and metadata responses but no reported write or availability impact.
The record
- CVE
- CVE-2026-85691
- Published
- Sep 4, 2026
- Updated
- Sep 10, 2026
- Vendor
- The Vibe Company
- Product
- MegaParse
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.0.55
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
No public exploit references are available in this record.
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