Categories
CVE-2026-34203 low CVSS 2.7

Vulnerability in nautobot (CVE-2026-34203)

Summary

Vulnerability in nautobot (CVE-2026-34203). Risk of unauthorized operations or information disclosure. Exploitable via AUTH_PASSWORD_VALIDATORS. Mitigation: upgrade to 3.0.10 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-34203 has been found in nautobot.
Attackers can target a specific entry point like AUTH_PASSWORD_VALIDATORS over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 2.7/10.
What to do: upgrade nautobot to 3.0.10 or later.
If unsure, ask your IT team or search "nautobot CVE-2026-34203" on the vendor's site.

CVE-2026-34203 (nautobot) — CWE-521 / CVSS v3 2.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: AUTH_PASSWORD_VALIDATORS / nautobot_config.py
Patched: 3.0.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-521) exists in nautobot. Attackers reach the vulnerable code path via AUTH_PASSWORD_VALIDATORS.

📍 Affected scope

Check the vendor advisory for the affected versions of nautobot. Attack surface: AUTH_PASSWORD_VALIDATORS / nautobot_config.py.

🔥 Severity

Severity: Low (CVSS 2.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nautobot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'nautobot' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nautobot を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade nautobot to 3.0.10

    ステージング環境で 3.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details