Is there a public exploit for CVE-2026-104250?

No public exploit for CVE-2026-104250 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-104250?

CVE-2026-104250 scores CVSS 6.1 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.23%.

What does CVE-2026-104250 affect?

CVE-2026-104250 affects Unstructured-IO unstructured.

6.1 Medium

The unstructured library provides open-source components for ingesting and pre-processing images and text documents, such as PDFs, HTML,…

CVE-2026-104250

The unstructured library provides open-source components for ingesting and pre-processing images and text documents, such as PDFs, HTML, Word docs, and many more. Prior to 0.24.1, partitionhtml(htmlparserversion="v2") and the VLM partitioner can preserve untrusted document tags, attributes, text, and link targets in metadata.textashtml, while elementstohtml() emits the result as an HTML document. The tohtml() path in unstructured/documents/ontology.py does not escape output or reject unsafe URL schemes, allowing event-handler attributes, attribute breakout markup, and javascript: links to survive parsing. When the generated HTML or textashtml is rendered in a browser, attacker-controlled script can execute in the viewer's origin, including in document-ingestion workflows where a privileged reviewer opens submitted content. This issue is fixed in version 0.24.1.

Assessment

CVSS: 6.1 (v3.1)
Severity: Medium
EPSS: 0.23% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 13 October 2026
Last updated: 16 October 2026
Affected: Unstructured-IO · unstructured
Weakness: CWE-116, CWE-79
Assigner: security-advisories@github.com

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 3 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-104250