Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text
CVE-2026-83801GHSA-56v6-2fhr-wxgq
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (nautobot 3.1.8, 2.4.37), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI nautobot
- Affected
- < 2.4.37>= 3.0.0, < 3.1.8
- Fixed in
- 2.4.37, 3.1.8
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-56v6-2fhr-wxgq lists affected ranges: PyPI nautobot >=0 =3.0.0 <3.1.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-56v6-2fhr-wxgq lists affected ranges: PyPI nautobot >=0 =3.0.0 <3.1.8 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2026-83801: 0.30% estimated exploitation activity in the next 30 days; percentile 22.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact What kind of vulnerability is it? Who is impacted? It has two related instances that share the same root cause: a user-controlled model field is assigned verbatim to a form field's helptext, which is rendered with Django's |safe filter (renderfield.html), bypassing auto-escaping. In both cases the script executes in the browser of any user who opens an affected create or edit form, including administrators and superusers. Because the payload runs in the victim's authenticated session, it can lead to actions performed as the victim, session/token theft, and further privilege escalation. Exploitation requires the victim to open an affected form. Relationship description A user who holds the add/change permission for Relationships (extras.addrelationship / extras.changerelationship) can set a Relationship's description to an HTML/JavaScript payload. That description is used as the help text of the relationship's form field and is rendered on the create/edit page of every object…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-56v6-2fhr-wxgq
- Revision 2 · amended ·
Amended from osv record GHSA-56v6-2fhr-wxgq
- Revision 1 · created ·
Published from ghsa record GHSA-56v6-2fhr-wxgq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-83801 Advisory: Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text IDs: CVE-2026-83801, GHSA-56v6-2fhr-wxgq Record: https://patchnext.com/advisories/cve-2026-83801 (revision 3, source checked 26 Oct 2026, 13:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: nautobot 3.1.8, 2.4.37. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI nautobot: affected < 2.4.37; >= 3.0.0, < 3.1.8; fixed in 2.4.37, 3.1.8 ## Suggested inspection (read-only) - `python -m pip show nautobot`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on nautobot. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-56v6-2fhr-wxgq (GitHub-reviewed advisory GHSA-56v6-2fhr-wxgq lists affected ranges: PyPI nautobot >=0 =3.0.0 <3.1.8) - Verified: https://osv.dev/vulnerability/GHSA-56v6-2fhr-wxgq (OSV record GHSA-56v6-2fhr-wxgq lists affected ranges: PyPI nautobot >=0 =3.0.0 <3.1.8 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…