GHSA-XMPV-J7P2-J873

Vulnerability from github – Published: 2026-03-31 23:07 – Updated: 2026-03-31 23:07
VLAI?
Summary
Nautobot: Management of users via REST API does not apply configured password validators
Details

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
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "nautobot"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.4.30"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "nautobot"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.0.0"
            },
            {
              "fixed": "3.0.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34203"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-521"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-31T23:07:23Z",
    "nvd_published_at": "2026-03-31T20:16:28Z",
    "severity": "LOW"
  },
  "details": "### Impact\n\nIn 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\u0027s `AUTH_PASSWORD_VALIDATORS` setting (which defaults to an empty list, i.e., no specific rules, but can be configured in Nautobot\u0027s `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.\n\nManagement of users via the Nautobot admin UI does correctly enforce configured password validation at this time.\n\n### Patches\n\nThe issue is resolved in Nautobot versions 2.4.30 and 3.0.10 and later.\n\n- https://github.com/nautobot/nautobot/pull/8778\n- https://github.com/nautobot/nautobot/pull/8779\n\n### Workarounds\n\nReview 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.\n\nIt may be appropriate furthermore to rotate passwords for any user accounts suspected to have been given weak passwords.\n\n### References\n\n- https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-AUTH_PASSWORD_VALIDATORS\n- http://docs.djangoproject.com/en/4.2/topics/auth/passwords/#password-validation",
  "id": "GHSA-xmpv-j7p2-j873",
  "modified": "2026-03-31T23:07:23Z",
  "published": "2026-03-31T23:07:23Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/nautobot/nautobot/security/advisories/GHSA-xmpv-j7p2-j873"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34203"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nautobot/nautobot/pull/8778"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nautobot/nautobot/pull/8779"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nautobot/nautobot/commit/589f7caf54124ad76bc9fcbb7bdcaa25627cd598"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nautobot/nautobot/commit/d1ef3135aa02fa07de061e8c085f8cce425fe8c9"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/nautobot/nautobot"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Nautobot: Management of users via REST API does not apply configured password validators"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…