CVE-2024-34707: Nautobot's BANNER_* configuration can be used to inject arbitrary HTML content into Nautobot pages
Impact A Nautobot user with admin privileges can modify the BANNERTOP, BANNERBOTTOM, and BANNERLOGIN configuration settings via the /admin/constance/config/ endpoint. Normally these settings are used to provide custom banner text at the top and bottom of all Nautobot web pages (or specifically on the login page in the case of BANNERLOGIN) but it was reported that an admin user can make use of these settings to…
Published May 13, 2024 · Updated May 14, 2024
Affected packages
nautobot
- Ecosystem
- PyPI
- Affected
- < 1.6.22
- Fixed in
- 1.6.22
- Check
pip show nautobot
nautobot
- Ecosystem
- PyPI
- Affected
- >= 2.0.0, < 2.2.4
- Fixed in
- 2.2.4
- Check
pip show nautobot
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A Nautobot user with admin privileges can modify the BANNER_TOP, BANNER_BOTTOM, and BANNER_LOGIN configuration settings via the /admin/constance/config/ endpoint. Normally these settings are used to provide custom banner text at the top and bottom of all Nautobot web pages (or specifically on the login page in the case of BANNER_LOGIN) but it was reported that an admin user can make use of these settings to inject arbitrary HTML, potentially exposing Nautobot users to security issues such as cross-site scripting (stored XSS).
Patches
_Has the problem been patched? What versions should users upgrade to?_
Patches will be released as part of Nautobot 1.6.22 and 2.2.4.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
As described in the Nautobot documentation, these settings are only configurable through the admin UI of Nautobot if they are *not* explicitly set to some non-empty value in the nautobot_config.py or equivalent Nautobot configuration file. Therefore, adding the following configuration to said file completely mitigates this vulnerability in both Nautobot 1.x and 2.x:
BANNER_LOGIN = " "
BANNER_TOP = " "
BANNER_BOTTOM = " "or alternately (Nautobot 2.x only), if those variables are not defined explicitly in your configuration file, setting the following environment variables for the Nautobot user account serves the same purpose:
NAUTOBOT_BANNER_LOGIN=" "
NAUTOBOT_BANNER_TOP=" "
NAUTOBOT_BANNER_BOTTOM=" "Limiting all users who do not need elevated privileges to non-admin access (is_superuser: False and is_staff: False) is a partial mitigation as well.
References
- https://github.com/nautobot/nautobot/pull/5697
- https://github.com/nautobot/nautobot/pull/5698
Credited to michaelpanorios.
References
- https://github.com/nautobot/nautobot/security/advisories/GHSA-r2hr-4v48-fjv3
- https://github.com/nautobot/nautobot/pull/5697
- https://github.com/nautobot/nautobot/pull/5698
- https://github.com/nautobot/nautobot/commit/4f0a66bd6307bfe0e0acb899233e0d4ad516f51c
- https://github.com/nautobot/nautobot/commit/f640aedc69c848d3d1be57f0300fc40033ff6423
- https://nvd.nist.gov/vuln/detail/CVE-2024-34707
- https://github.com/advisories/GHSA-r2hr-4v48-fjv3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-83801
Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text
medium5.4Sep 22, 2026CVE-2026-83805
Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs
medium6.4Sep 22, 2026CVE-2026-44794
Nautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
medium5.4May 13, 2026CVE-2026-44796
Nautobot: Object bulk rename UI actions vulnerable to denial of service by crafted regular expression (REDoS)
medium6.5May 13, 2026CVE-2026-44797
Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
high8.5May 13, 2026CVE-2026-44798
Nautobot: GitRepository.current_head field should not be writable through REST API
high7.1May 13, 2026
