Quick answers
- Is CVE-2026-44796 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44796 being exploited in the wild.
- How severe is CVE-2026-44796?
- Medium severity, with a CVSS score of 6.5, published 28 May 2026.
- Which products and versions are affected?
- nautobot (PyPI) ECOSYSTEM:introduced=0,fixed=2.4.33,introduced=3.0.0,fixed=3.1.2, ECOSYSTEM:introduced=3.0.0a2,fixed=3.1.2.
- Is there a fix for CVE-2026-44796?
- Yes. nautobot (PyPI): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44796 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44796?
- Check whether you run nautobot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nautobot (PyPI): upgrade to 3.1.2 or later
pip install "nautobot>=3.1.2"
Technical details
A Regular Expression Denial of Service (REDoS) vulnerability exists in Nautobot's object-bulk-rename UI endpoints, such as `/dcim/interfaces/rename/`. The vulnerability is rooted in the `find` field when the `use_regex` flag is enabled, where inefficient regular expression complexity (CWE-1333) allows for uncontrolled resource consumption (CWE-400). An authenticated attacker with network access can provide a maliciously crafted regex that triggers catastrophic backtracking, consuming excessive CPU cycles and leading to an application-wide denial of service. The issue has been mitigated in versions 2.4.33 and 3.1.2 by implementing a general-purpose timeout for regex evaluation in these specific endpoints.
Affected products
- Nautobot Nautobot >= 3.0.0a2, < 3.1.2; < 2.4.33
Identifiers
- CVE-2026-44796
- GHSA-qrpw-gjvh-x5gm
- PYSEC-2026-2226
Timeline
- 2026-05-08: disclosed: Initial disclosure by reporter
- 2026-05-13: advisory: GitHub Advisory published
- 2026-05-28: other: NVD publication date