CVE-2025-49142: nautobot · Improper Neutralization of Special Elements Used in a Template Engine
Affects nautobotSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 2.4.10 or 1.6.32 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.10, 1.6.32
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade nautobot/nautobot to 2.4.10 or 1.6.32.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPInautobot/nautobotpkg:pypi/nautobot/nautobotOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade Nautobot installations to version 1.6.32 or 2.4.10 or later, where the vulnerability is fixed. 2. Restrict permissions rigorously: limit the ability to create or modify templates, computed fields, and custom links to a minimal set of trusted administrators. 3. Review and audit existing templates for any suspicious or overly permissive configurations that could exploit the Jinja2 engine. 4. Implement network segmentation and firewall rules to restrict access to Nautobot management interfaces to trusted networks and users only. 5. Monitor logs for unusual template rendering activity or access patterns that could indicate exploitation attempts. 6. Educate administrators about the risks of template injection and the importance of secure configuration. 7. Consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious template-related payloads. 8. Regularly back up Nautobot data and configuration to enable recovery in case of unauthorized modifications.
Description
Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions prior to 2.4.10 or prior to 1.6.32 are potentially affected. Due to insufficient security configuration of the Jinja2 templating feature used in computed fields, custom links, etc.in Nautobot, a malicious user could configure this feature set in ways that could expose the value of Secrets defined in Nautobot when the templated content is rendered or that could call Python APIs to modify data within Nautobot when the templated content is rendered, bypassing the object permissions assigned to the viewing user. Nautobot versions 1.6.32 and 2.4.10 will include fixes for the vulnerability. The vulnerability can be partially mitigated by configuring object permissions appropriately to limit certain actions to only trusted users.
References
- github.com/nautobot/nautobot/security/advisories/GHSA-wjw6-95h5-4jpx (opens in a new tab)
- github.com/nautobot/nautobot/pull/7417 (opens in a new tab)
- github.com/nautobot/nautobot/pull/7429 (opens in a new tab)
- docs.djangoproject.com/en/4.2/ref/templates/api/ (opens in a new tab)
- jinja.palletsprojects.com/en/stable/sandbox (opens in a new tab)