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). 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-AUTHPASSWORDVALIDATORS - http://docs.djangoproject.com/en/4.2/topics/auth/passwords/#password-validation
Other sources
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 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). 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/nautobotto a version that resolves this vulnerability.Fixed in 3.0.10 - Upgrade
Upgrade
pip/nautobotto a version that resolves this vulnerability.Fixed in 2.4.30 - Upgrade
Upgrade
nautobotto a version that resolves this vulnerability.Fixed in 2.4.30 - Upgrade
Upgrade
nautobotto a version that resolves this vulnerability.Fixed in 3.0.10 - Compensating control
Review which users have been granted object permissions to create and modify user accounts and restrict access as appropriate for users accessing the Nautobot REST API (and having access tokens for the REST API).
- Operational
Rotate passwords for any user accounts suspected to have been given weak passwords.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-34203?
CVE-2026-34203 has been classified with a significant severity due to the failure in enforcing password validation rules.
How do I fix CVE-2026-34203?
To fix CVE-2026-34203, upgrade Nautobot to version 2.4.30 or 3.0.10 or later to ensure password validators are applied.
Which versions of Nautobot are affected by CVE-2026-34203?
CVE-2026-34203 affects Nautobot versions prior to 2.4.30 and 3.0.10.
What is the impact of exploiting CVE-2026-34203?
Exploiting CVE-2026-34203 can allow unauthorized users to create or modify accounts without enforcing the configured password complexity requirements.
Does CVE-2026-34203 apply to all Nautobot API operations?
CVE-2026-34203 specifically affects user management operations via the REST API, not all API operations.