Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3amended

Nautobot may allows uploaded media files to be accessible without authentication

CVE-2025-49143GHSA-rh67-4c8j-hjjh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nautobot 2.4.10, 1.6.32), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI nautobot

    Affected
    < 1.6.32>= 2.0.0, < 2.4.10
    Fixed in
    1.6.32, 2.4.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N · score source
EPSS
  • CVE-2025-49143: 0.44% estimated exploitation activity in the next 30 days; percentile 38.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rh67-4c8j-hjjh

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-rh67-4c8j-hjjh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-49143

Advisory: Nautobot may allows uploaded media files to be accessible without authentication
IDs: CVE-2025-49143, GHSA-rh67-4c8j-hjjh
Record: https://patchnext.com/advisories/cve-2025-49143 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nautobot 2.4.10, 1.6.32. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nautobot: affected < 1.6.32; >= 2.0.0, < 2.4.10; fixed in 1.6.32, 2.4.10

## Suggested inspection (read-only)
- `python -m pip show nautobot`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nautobot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rh67-4c8j-hjjh (OSV record GHSA-rh67-4c8j-hjjh lists affected ranges: PyPI nautobot >=0 =2.0.0 <2.4.10 (fixed))
- Verified: https://github.com/advisories/GHSA-rh67-4c8j-hjjh (GitHub-reviewed advisory GHSA-rh67-4c8j-hjjh lists affected ranges: PyPI nautobot >=0 =2.0.0 <2.4.10)

Commands are suggestions: review each one before running it.

Loading voting…