CVE-2025-49143: nautobot · Information Exposure
Affects nautobotSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.6.32 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.32
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation 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 26 Oct 2026.
What to do
Upgrade nautobot to 1.6.32.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPInautobotpkg:pypi/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
European organizations should immediately upgrade Nautobot installations to versions 1.6.32 or 2.4.10 or later to ensure the authentication enforcement is in place. Until upgrades can be performed, organizations should restrict network access to the MEDIA_ROOT directory endpoint using network segmentation, firewall rules, or reverse proxy authentication layers to prevent anonymous access. Additionally, organizations should audit existing uploaded files for sensitive content and consider removing or re-uploading files with stricter access controls. Implementing monitoring and alerting for unusual access patterns to these endpoints can help detect potential exploitation attempts. Regularly reviewing and updating access control policies for network management platforms is recommended to prevent similar issues. Finally, organizations should educate administrators about the importance of applying security patches promptly and verifying that authentication mechanisms are correctly enforced on all endpoints serving sensitive data.
Description
Nautobot is a Network Source of Truth and Network Automation Platform. Prior to v2.4.10 and v1.6.32 , files uploaded by users to Nautobot's MEDIA_ROOT directory, including DeviceType image attachments as well as images attached to a Location, Device, or Rack, are served to users via a URL endpoint that was not enforcing user authentication. As a consequence, such files can be retrieved by anonymous users who know or can guess the correct URL for a given file. Nautobot v2.4.10 and v1.6.32 address this issue by adding enforcement of Nautobot user authentication to this endpoint.
References
- github.com/nautobot/nautobot/security/advisories/GHSA-rh67-4c8j-hjjh (opens in a new tab)
- github.com/nautobot/nautobot/pull/6672 (opens in a new tab)
- github.com/nautobot/nautobot/pull/6703 (opens in a new tab)
- github.com/nautobot/nautobot/commit/9c892dc300429948a4714f743c9c2879d8987340 (opens in a new tab)
- github.com/nautobot/nautobot/commit/d99a53b065129cff3a0fa9abe7355a9ef1ad4c95 (opens in a new tab)