Nautobot up to 2.4.29/3.0.9 REST API nautobot_config.py weak password

Summaryinfo

A vulnerability, which was classified as critical, has been found in Nautobot up to 2.4.29/3.0.9. This impacts an unknown function of the file nautobot_config.py of the component REST API. Performing a manipulation results in weak password. This vulnerability is known as CVE-2026-34203. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Nautobot up to 2.4.29/3.0.9. This affects an unknown functionality of the file nautobot_config.py of the component REST API. The manipulation with an unknown input leads to a weak password vulnerability. CWE is classifying the issue as CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-34203 since 03/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation requires an enhanced level of successful authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

Upgrading to version 2.4.30 or 3.0.10 eliminates this vulnerability. Applying the patch 589f7caf54124ad76bc9fcbb7bdcaa25627cd598 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Nautobot

Version

• 2.4.0
• 2.4.1
• 2.4.2
• 2.4.3
• 2.4.4
• 2.4.5
• 2.4.6
• 2.4.7
• 2.4.8
• 2.4.9
• 2.4.10
• 2.4.11
• 2.4.12
• 2.4.13
• 2.4.14
• 2.4.15
• 2.4.16
• 2.4.17
• 2.4.18
• 2.4.19
• 2.4.20
• 2.4.21
• 2.4.22
• 2.4.23
• 2.4.24
• 2.4.25
• 2.4.26
• 2.4.27
• 2.4.28
• 2.4.29
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7
• 3.0.8
• 3.0.9

License

• open-source

Website

• Product: https://github.com/nautobot/nautobot/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion