Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.7amended

Unauthenticated db-file-storage views

CVE-2023-50263GHSA-75mc-3pjc-727q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nautobot 2.0.6, 1.6.7), 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.1.0, < 1.6.7>= 2.0.0, < 2.0.6
    Fixed in
    2.0.6, 1.6.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2023-50263: 0.75% estimated exploitation activity in the next 30 days; percentile 55.14 (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 In Nautobot 1.x and 2.0.x, the URLs /files/get/?name=... and /files/download/?name=... are used to provide admin access to files that have been uploaded as part of a run request for a Job that has FileVar inputs. Under normal operation these files are ephemeral and are deleted once the Job in question runs. It was reported by @kircheneer that in the default implementation used in Nautobot, as provided by django-db-file-storage, these URLs do not by default require any user authentication to access; they should instead be restricted to only users who have permissions to view Nautobot's FileProxy model instances. Note that no URL mechanism is provided for listing or traversal of the available file name values, so in practice an unauthenticated user would have to guess names to discover arbitrary files for download, but if a user knows the file name/path value, they can access it without authenticating, so we are considering this a vulnerability. Patches Fixes will be included in…

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

    Amended from ghsa record GHSA-75mc-3pjc-727q

  2. Revision 1 · created ·

    Published from osv record GHSA-75mc-3pjc-727q

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-2023-50263

Advisory: Unauthenticated db-file-storage views
IDs: CVE-2023-50263, GHSA-75mc-3pjc-727q
Record: https://patchnext.com/advisories/cve-2023-50263 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nautobot 2.0.6, 1.6.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nautobot: affected >= 1.1.0, < 1.6.7; >= 2.0.0, < 2.0.6; fixed in 2.0.6, 1.6.7

## 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-75mc-3pjc-727q (OSV record GHSA-75mc-3pjc-727q lists affected ranges: PyPI nautobot >=1.1.0 =2.0.0 <2.0.6 (fixed))
- Verified: https://github.com/advisories/GHSA-75mc-3pjc-727q (GitHub-reviewed advisory GHSA-75mc-3pjc-727q lists affected ranges: PyPI nautobot >=1.1.0 =2.0.0 <2.0.6)

Commands are suggestions: review each one before running it.

Loading voting…