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.
CVE-2026-83801
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (5)
Auto-updated Sep 22, 2026v3.1.8 - 2026-07-17
Patch available: nautobot/nautobot v3.1.8
https://github.com/nautobot/nautobot/releases/tag/v3.1.8v2.4.37 - 2026-07-17
Patch available: nautobot/nautobot v2.4.37
https://github.com/nautobot/nautobot/releases/tag/v2.4.37commit f8a62466f3eb (nautobot/nautobot)
Fix landed in nautobot/nautobot commit f8a62466f3eb — awaiting tagged release
https://github.com/nautobot/nautobot/commit/f8a62466f3ebc42759a6373e7c79b0cad5751c2fcommit e6ff20d50e07 (nautobot/nautobot)
Fix landed in nautobot/nautobot commit e6ff20d50e07 — awaiting tagged release
https://github.com/nautobot/nautobot/commit/e6ff20d50e0759135c6d278e7b2ceec56ed9b3c8Stored cross-site scripting (XSS) in object create/edit form help text · Advisory · nautobot/nautobot · GitHub
https://github.com/nautobot/nautobot/security/advisories/GHSA-56v6-2fhr-wxgqVendor Advisories for CVE-2026-83801(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nautobot | 1.0.0 ... 2.4.9 (194 versions) | 2.4.37 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 18:25 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 15:20 UTCEG score recompute
- 2026-09-23 15:15 UTCEG score recompute
- 2026-09-22 20:32 UTCEG score recompute
- 2026-09-22 19:53 UTCEG score recompute
- 2026-09-22 19:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-83801?
When was CVE-2026-83801 disclosed?
Is CVE-2026-83801 actively exploited?
What is the CVSS score of CVE-2026-83801?
How do I remediate CVE-2026-83801?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-83801
Is Your Infrastructure Affected by CVE-2026-83801?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.