django-docutils local file disclosure and SSRF in reStructuredText parser
django-docutils 0.29.0 and earlier is affected when it renders attacker-controlled or lower-trust RST without its own safe Docutils configuration. Fixed in 0.30.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.30.0
- Who is exposed
- Default setups
Summary
Django-docutils, a reStructuredText library for Django, has an issue where rendering paths pass untrusted reStructuredText to Docutils with unsafe defaults. A remote attacker who can influence the rendered content, without logging in, can read local files, trigger server-side URL requests, or inject stored script-capable content.
Written by a model
Original description
django-docutils provides reStructuredText support for Django. Prior to 0.30.0, public rendering paths including publish_doctree, publish_html_from_source, publish_html_from_doctree, publish_parts_from_doctree, the {% rst %} template tag, the rst template filter, DocutilsTemplates, and DocutilsView pass lower-trust reStructuredText to Docutils without disabling file_insertion_enabled, raw_enabled, ambient docutils.conf processing, or unsafe URI schemes and without consistently sanitizing doctrees. An attacker who can influence rendered reStructuredText can use include or csv-table directives to read local files or cause server-side URL requests, or use raw HTML and unsafe URI output to inject stored script-capable content. Applications that render only trusted static reStructuredText are not affected unless attackers can influence it. This issue is fixed in version 0.30.0.
Who should check
Teams running django-docutils 0.29.0 or earlier that render user-influenced RST, such as comments, wiki pages, profile bios, CMS fields or uploaded documents.
Not fixed by: UI escaping after rendering does not stop file disclosure.
“Affected versions: <= 0.29.0”
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 0.30.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-59988 (django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-59988 (entry last updated 2026-11-19):
Affected:
- tony django-docutils: fixed in 0.30.0
Fixed versions: 0.30.0.
Conditions (all must be true for the bug to be hit):
- django-docutils versions before 0.30.0 (affected versions <= 0.29.0). (source: https://github.com/tony/django-docutils/security/advisories/GHSA-86mf-q4h5-69gp)
- The application renders attacker-controlled or lower-trust RST through django-docutils without its own safe Docutils configuration. (source: https://github.com/tony/django-docutils/security/advisories/GHSA-86mf-q4h5-69gp)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-59988 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59988 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tony/django-docutils/security/advisories/GHSA-86mf-q4h5-69gp
- https://github.com/tony/django-docutils/pull/457
- https://github.com/tony/django-docutils/commit/274caaf14c2368fafeb45f178094a34ba538f067
- https://github.com/tony/django-docutils/commit/57fd751a10ce2969e4ca2bde6a9094fa2e2ba0dd
- https://github.com/tony/django-docutils/blob/v0.30.0/CHANGES
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-59988
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-59988"}.Affected versions
- tony django-docutilsfixed in 0.30.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · tony/django-docutils · Advisory GHSA-86mf-q4h5-69gp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-59988 |
| Record | NVD · CVE-2026-59988 |
| Other links 4 | |
| Repository | GitHub · tony/django-docutils · Pull request #457 |
| Repository | GitHub · tony/django-docutils · Commit 274caaf1 |
| Repository | GitHub · tony/django-docutils · Commit 57fd751a |
| Repository | GitHub · tony/django-docutils · CHANGES |
Questions about CVE-2026-59988
Is CVE-2026-59988 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The unsafe Docutils defaults let an attacker who can influence rendered RST read files the Django worker process can read, trigger server-side requests through URL-backed directives, or inject raw HTML and JavaScript into the rendered output.
Source: github.com
Which versions are affected by CVE-2026-59988?
django-docutils: before 0.30.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions before 0.30.0 (0.29.0 and earlier) are affected, and only when an application renders attacker-controlled or lower-trust RST through django-docutils without its own safe Docutils configuration. To check, look at the installed django-docutils version and whether the application sets its own safe Docutils configuration.
Source: github.com
How do I fix CVE-2026-59988?
Upgrade django-docutils to 0.30.0 or later, the fixed version.
Source: github.com
Related
- CVE-2026-77312Flyto2 Core: Arbitrary file write via unguarded data.*/file. modules (incomplete fix of CVE-2026-67429)
- CVE-2026-114516Etherpad: Pre-auth arbitrary file read
- CVE-2026-130235Improper Request URL Validation in the Okta .NET SDK Abstractions Library
- CVE-2026-77315Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
- CVE-2026-61798netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
- CVE-2026-84273IBM Guardium Data Protection Path Traversal
No corrections so far. Something wrong on this page? Report an error.