nautobot
Affected
- introduced
0, fixed1.6.32(ecosystem)
Fixed versions
1.6.32
Fix
- Fixed version
1.6.32pip install --upgrade nautobot==1.6.32
Advisory
Also known as: CVE-2025-49143, PYSEC-2026-1689
Nautobot may allows uploaded media files to be accessible without authentication
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?_
Medium Basis: The source's own band: MODERATE
0, fixed 1.6.32 (ecosystem)1.6.32
1.6.32pip install --upgrade nautobot==1.6.322.0.0, fixed 2.4.10 (ecosystem)2.4.10
2.4.10pip install --upgrade nautobot==2.4.10Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0