CVE-2026-34203: Nautobot: Management of users via REST API does not apply configured password validators
Impact In Nautobot versions prior to 2.4.30 or prior to 3.0.10, user creation and editing via the REST API fails to apply the password validation rules defined by Django's AUTHPASSWORDVALIDATORS setting (which defaults to an empty list, i.e., no specific rules, but can be configured in Nautobot's nautobotconfig.py to apply various rules if desired).
Published Mar 31, 2026
Affected packages
nautobot
- Ecosystem
- PyPI
- Affected
- < 2.4.30
- Fixed in
- 2.4.30
- Check
pip show nautobot
nautobot
- Ecosystem
- PyPI
- Affected
- >= 3.0.0, < 3.0.10
- Fixed in
- 3.0.10
- Check
pip show nautobot
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In Nautobot versions prior to 2.4.30 or prior to 3.0.10, user creation and editing via the REST API fails to apply the password validation rules defined by Django's AUTH_PASSWORD_VALIDATORS setting (which defaults to an empty list, i.e., no specific rules, but can be configured in Nautobot's nautobot_config.py to apply various rules if desired). This can potentially allow for the creation or modification of users to have passwords that are weak or otherwise do not comply with configured standards.
Management of users via the Nautobot admin UI does correctly enforce configured password validation at this time.
Patches
The issue is resolved in Nautobot versions 2.4.30 and 3.0.10 and later.
- https://github.com/nautobot/nautobot/pull/8778
- https://github.com/nautobot/nautobot/pull/8779
Workarounds
Review which users have been granted object permissions to create and modify user accounts as well as having access tokens for the REST API, and restrict access as appropriate.
It may be appropriate furthermore to rotate passwords for any user accounts suspected to have been given weak passwords.
References
- https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-AUTH_PASSWORD_VALIDATORS
- http://docs.djangoproject.com/en/4.2/topics/auth/passwords/#password-validation
Credited to morimori-dev.
References
- https://github.com/nautobot/nautobot/security/advisories/GHSA-xmpv-j7p2-j873
- https://nvd.nist.gov/vuln/detail/CVE-2026-34203
- https://github.com/nautobot/nautobot/pull/8778
- https://github.com/nautobot/nautobot/pull/8779
- https://github.com/nautobot/nautobot/commit/589f7caf54124ad76bc9fcbb7bdcaa25627cd598
- https://github.com/nautobot/nautobot/commit/d1ef3135aa02fa07de061e8c085f8cce425fe8c9
- https://github.com/advisories/GHSA-xmpv-j7p2-j873
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
