dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-45553

HIGH · 7.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NiceGUI is a Python-based UI framework. Prior to version 3.12.0, ui.restructured_text() renders reStructuredText server-side with Docutils without disabling file insertion directives. When a NiceGUI application passes attacker-controlled content to ui.restructured_text(), an attacker can use standard Docutils directives (include, csv-table with :file:, raw with :file:) to read local files readable by the NiceGUI server process. Applications that only pass trusted static strings to ui.restructured_text() are not affected. This issue has been patched in version 3.12.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NiceGUI's ui.restructured_text() renders reStructuredText using Docutils without disabling file insertion directives (include, csv-table with :file:, raw with :file:). When attacker-controlled content is passed to this function, attackers can read local files accessible to the server process by embedding special Docutils directives.

MitigationUpgrade NiceGUI to version 3.12.0 or later. If upgrading is not immediately possible, ensure ui.restructured_text() only receives trusted static strings and never user-supplied input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check NiceGUI version
    Run 'pip show nicegui' or 'python -c "import nicegui; print(nicegui.__version__)"' to see the installed version
    Affected if Version is lower than 3.12.0
  2. Find ui.restructured_text usage
    Search codebase for 'ui.restructured_text(' or '.restructured_text(' patterns
    Affected if This function is called in the application code
  3. Trace input source to restructured_text
    Review each call to ui.restructured_text() and trace what data is passed as the argument - check if it comes from request parameters, user input, databases, or external sources
    Affected if The argument to restructured_text() derives from untrusted user input, HTTP requests, or any attacker-controlled source
  4. Verify file access permissions
    Check what filesystem permissions the NiceGUI server process has access to - list readable directories and files accessible to the user running the application
    Affected if The server process has access to sensitive files that should not be exposed via the web interface

You are affected if NiceGUI version is below 3.12.0 AND your code uses ui.restructured_text() with any content that originates from users or untrusted sources, allowing potential local file disclosure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade NiceGUI to version 3.12.0 or later. If upgrading is not immediately possible, ensure ui.restructured_text() only receives trusted static strings and never user-supplied input.

Recommended fix High confidence

NiceGUI version 3.12.0

  1. Identify all instances of ui.restructured_text() in your codebase
  2. Audit each call to ui.restructured_text() to determine if it processes user-supplied or attacker-controlled content
  3. If attacker-controlled content is passed to ui.restructured_text(), upgrade NiceGUI to version 3.12.0 or later by running: pip install nicegui>=3.12.0
  4. After upgrading, verify that the ui.restructured_text() function properly sanitizes or restricts Docutils directives
  5. If you cannot upgrade immediately and must continue using an affected version, implement input validation to ensure only trusted static strings are passed to ui.restructured_text()

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45553 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data