Vulnerability in nautobot (CVE-2026-44796)
Summary
Vulnerability in nautobot (CVE-2026-44796). Risk of unauthorized operations or information disclosure. Exploitable via find. Mitigation: upgrade to 2.4.33 or later.
Original description
The description as published by the source.
Impact
Nautobot UI object-bulk-rename endpoints (for example, /dcim/interfaces/rename/) were vulnerable to application-wide denial of service via maliciously crafted regular expressions in the find field in combination with the use_regex flag.
Patches
A general-purpose timeout has been added to these endpoints in Nautobot v2.4.33 and v3.1.2, which ensures that the request will fail early with an appropriate message if regular expression evaluation takes more than a short period of time, instead of continuing to execute for an indefinite duration.
Workarounds
No known workaround has been identified at this time.
References
- 2.4.33 (patch)
- 3.1.2 (patch)
Source: GitHub Security Advisories (Global) 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-44796 has been found in nautobot.
Attackers can target a specific entry point like find over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade nautobot to 2.4.33 or later.
If unsure, ask your IT team or search "nautobot CVE-2026-44796" on the vendor's site.
CVE-2026-44796 (nautobot) — CWE-400 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: find / use_regex
Patched: 2.4.33 — apply immediately
Workaround: No known workaround has been identified at this time.
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.
A vulnerability (CWE-400) exists in nautobot. Attackers reach the vulnerable code path via find.
Check the vendor advisory for the affected versions of nautobot. Attack surface: find / use_regex.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.4.33.
Workaround: No known workaround has been identified at this time.
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
-
1Identify exposure identify
grep -r 'nautobot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nautobotを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No known workaround has been identified at this time.パッチが適用されるまでの応急処置として、No known workaround has been identified at this time. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade nautobot to 2.4.33ステージング環境で 2.4.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com