Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

Nautobot: Stored cross-site scripting (XSS) in object create/edit form help textGHSA-56v6-2fhr-wxgq

MEDIUMFix: nautobot/nautobot@e6ff20d

GHSA-56v6-2fhr-wxgq is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in nautobot. A fix is available for nautobot — see the affected versions and patch details below.

Also known asCVE-2026-83801PYSEC-2026-4110
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-56v6-2fhr-wxgq.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk
0.00%0.24%0.48%0.72%0.2%0.2%Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-56v6-2fhr-wxgq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐍nautobot🐍nautobot

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 help_text, which is rendered with Django's |safe filter (render_field.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.add_relationship / extras.change_relationship) 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 type the relationship applies to.

Module Family name

A user who holds the add/change permission for Module Families (dcim.add_modulefamily / dcim.change_modulefamily) can put a payload in a Module Family name, which is interpolated into the module_family field's help text on the Module "Install module" form for any module bay assigned to that family.

Patches

Has the problem been patched? What versions should users upgrade to?

Fixes are available in Nautobot v2.4.37+ & v3.1.8+

Note: The underlying weakness exists in earlier EOL versions of Nautobot (v1.x). Users on those older EOL versions are highly encouraged to upgrade to a supported version.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

There is no configuration-only fix. To remediate without upgrading:

  • Restrict the extras.add_relationship / extras.change_relationship and dcim.add_modulefamily / dcim.change_modulefamily permissions to fully trusted administrators only.
  • Audit existing Relationship description values and Module Family name values for embedded HTML / <script> content and remove any payloads.

Note that limiting who can open create/edit forms does not fully mitigate the issue, since the payload targets any user (including admins) who opens an affected form.

Credit

Credit for this discovery goes to Habibullo Izzatilloyev.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPInautobotall versions2.4.37pip install --upgrade 'nautobot==2.4.37'
🐍PyPInautobot≥ 3.0.0&&< 3.1.83.1.8pip install --upgrade 'nautobot==3.1.8'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nautobot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update nautobot to 2.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56v6-2fhr-wxgq is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### 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 `help_text`, which is rendered with Django's `|safe` filter (`render_field.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 pr
O3 Security · Impact-Aware SCA

Is GHSA-56v6-2fhr-wxgq in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
Nautobot: Stored cross-site scripting (XSS) in object…