# CVE-2026-83801: Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text

> Authenticated users can inject malicious scripts into relationship or module family fields, leading to code execution and privilege escalation in victim sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-56v6-2fhr-wxgq, PYSEC-2026-4110

## What is CVE-2026-83801?

CVE-2026-83801 is a medium-severity cross-site scripting vulnerability in nautobot, published on 22 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Nautobot is a Network Source of Truth and Network Automation Platform. Prior to 2.4.37 and 3.1.8, a user with extras.add_relationship or extras.change_relationship permission can store HTML or JavaScript in a Relationship description, and a user with dcim.add_modulefamily or dcim.change_modulefamily permission can store it in a Module Family name. Nautobot assigns these values to form field help_text rendered by render_field.html through Django's |safe filter without adequate neutralization. The stored content executes in the authenticated browser session of any user, including an administrator or superuser, who opens an affected create or edit form. This can enable actions as the victim, session or token theft, and further privilege escalation. This issue is fixed in versions 2.4.37 and 3.1.8.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-83801?

5 open source packages ship an affected version, including nautobot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nautobot` | PyPI | All versions | 2.4.37, 3.1.8 |
| `nautobot` | PyPI | All versions | 2.4.37 |
| `nautobot` | PyPI | All versions | 2.4.37 |
| `nautobot` | PyPI | From 3.0.0 | 3.1.8 |
| `nautobot` | PyPI | From 3.0.0 | 3.1.8 |

## How do I fix CVE-2026-83801?

Upgrade nautobot to a fixed version for your release line: 2.4.37 or 3.1.8.

## Is CVE-2026-83801 being exploited?

There is no known exploitation of CVE-2026-83801 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-83801 and fix it if it is affected.

What it is: CVE-2026-83801 is a medium-severity cross-site scripting vulnerability in nautobot, published on 22 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-83801 in the wild and no public exploit code.

Affected packages and fixed versions:
- nautobot (PyPI): affected all versions; fixed in 2.4.37, 3.1.8
- nautobot (PyPI): affected all versions; fixed in 2.4.37
- nautobot (PyPI): affected all versions; fixed in 2.4.37
- nautobot (PyPI): affected from 3.0.0; fixed in 3.1.8
- nautobot (PyPI): affected from 3.0.0; fixed in 3.1.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-83801/ (Markdown: https://insights.sbomify.com/CVE-2026-83801/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-83801
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-83801
- OSV: https://osv.dev/vulnerability/CVE-2026-83801

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-83801/
Summaries are generated and may contain mistakes; the official description above is the record.