CVE-2025-49143: Nautobot may allows uploaded media files to be accessible without authentication
Impact Files uploaded by users to Nautobot's MEDIAROOT 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.
Published Jun 10, 2025
Affected packages
nautobot
- Ecosystem
- PyPI
- Affected
- < 1.6.32
- Fixed in
- 1.6.32
- Check
pip show nautobot
nautobot
- Ecosystem
- PyPI
- Affected
- >= 2.0.0, < 2.4.10
- Fixed in
- 2.4.10
- Check
pip show nautobot
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
For DeviceType image attachments, a mitigating factor is that no URL endpoint exists for listing the contents of the devicetype-images/ subdirectory, and the file names are as specified by the uploading user, so any given DeviceType image attachment can only be retrieved by correctly guessing its file name.
Similarly, for all other image attachments, while the images *can* be listed by accessing the /api/extras/image-attachments/ endpoint *as an authenticated user only*, absent that authenticated access, accessing the files would again require guessing file names correctly.
Patches
Nautobot v2.4.10 and v1.6.32 will address this issue by adding enforcement of Nautobot user authentication to this endpoint.
Workarounds
No workaround other than applying the patch given in https://github.com/nautobot/nautobot/pull/6672 (2.x) or https://github.com/nautobot/nautobot/pull/6703 (1.6)
References
_Are there any links users can visit to find out more?_
- https://github.com/nautobot/nautobot/commit/9c892dc300429948a4714f743c9c2879d8987340
- https://github.com/nautobot/nautobot/commit/d99a53b065129cff3a0fa9abe7355a9ef1ad4c95
References
- https://github.com/nautobot/nautobot/security/advisories/GHSA-rh67-4c8j-hjjh
- https://nvd.nist.gov/vuln/detail/CVE-2025-49143
- https://github.com/nautobot/nautobot/pull/6672
- https://github.com/nautobot/nautobot/pull/6703
- https://github.com/nautobot/nautobot/commit/9c892dc300429948a4714f743c9c2879d8987340
- https://github.com/nautobot/nautobot/commit/d99a53b065129cff3a0fa9abe7355a9ef1ad4c95
- https://github.com/advisories/GHSA-rh67-4c8j-hjjh
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-83801
Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text
medium5.4Sep 22, 2026CVE-2026-83805
Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs
medium6.4Sep 22, 2026CVE-2026-44794
Nautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
medium5.4May 13, 2026CVE-2026-44796
Nautobot: Object bulk rename UI actions vulnerable to denial of service by crafted regular expression (REDoS)
medium6.5May 13, 2026CVE-2026-44797
Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
high8.5May 13, 2026CVE-2026-44798
Nautobot: GitRepository.current_head field should not be writable through REST API
high7.1May 13, 2026
