CVE-2026-34203

### 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

Nautobot is a Network Source of Truth and Network Automation Platform. Prior to versions 2.4.30 and 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. This issue has been patched in versions 2.4.30 and 3.0.10.