Low

Unauthenticated views may expose information to anonymous users

  • Disclosed: 26.03.2024
  • Updated: 11.10.2026 15:17

Impact

A number of Nautobot URL endpoints were found to be improperly accessible to unauthenticated (anonymous) users, including the following:

  • /api/graphql/ (1)
  • /api/users/users/session/ (Nautobot 2.x only; the only information exposed to an anonymous user is which authentication backend classes are enabled on this Nautobot instance)
  • /dcim/racks/<uuid:pk>/dynamic-groups/ (1)
  • /dcim/devices/<uuid:pk>/dynamic-groups/ (1)
  • /extras/job-results/<uuid:pk>/log-table/
  • /extras/secrets/provider/<str:provider_slug>/form/ (the only information exposed to an anonymous user is the fact that a secrets provider with the given slug (e.g. environment-variable or text-file) is supported by this Nautobot instance)
  • /ipam/prefixes/<uuid:pk>/dynamic-groups/ (1)
  • /ipam/ip-addresses/<uuid:pk>/dynamic-groups/ (1)
  • /virtualization/clusters/<uuid:pk>/dynamic-groups/ (1)
  • /virtualization/virtual-machines/<uuid:pk>/dynamic-groups/ (1)

(1) These endpoints will not disclose any Nautobot data to an unauthenticated user unless the Nautobot configuration variable EXEMPT_VIEW_PERMISSIONS is changed from its default value (an empty list) to permit access to specific data by unauthenticated users.

Of these endpoints, the only one that poses any significant risk of sensitive information disclosure under normal Nautobot operation with a default configuration is /extras/job-results/<uuid:pk>/log-table/. This endpoint returns an HTML table containing all of the logs associated with the specified JobResult; while these logs may contain sensitive information depending on the Jobs executed in Nautobot, this exposure is mitigated somewhat by the fact that any attacker would have to have prior knowledge of the existence of a JobResult with a particular UUID.

In the interest of full disclosure, the following additional endpoints were also accessible to anonymous users, but do not disclose any sensitive data when accessed (only a listing of other API endpoints).

  • /api/
  • /api/circuits/
  • /api/dcim/
  • /api/extras/
  • /api/ipam/
  • /api/plugins/
  • /api/tenancy/
  • /api/users/
  • /api/virtualization/

All of the above endpoints have been corrected to require user authentication, with the exception of /api/users/users/session/ which is unused at this time and therefore has been simply removed from Nautobot 2.1.9. Additionally, we have added test automation which enumerates available Nautobot URL endpoints and verifies that appropriate authentication requirements are in place; this test was instrumental in identifying the above comprehensive list.

Patches

Fixes will be included in Nautobot 1.6.16 and 2.1.9.

Workarounds

Partial workaround: If your configuration includes a non-default value for EXEMPT_VIEW_PERMISSIONS (the Nautobot default is an empty list), reverting it to default will prevent exposure of Nautobot information to unauthenticated users via the endpoints marked with (1) above.

References

Are there any links users can visit to find out more?

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) nautobot < 1.6.16, >= 2.0.0, < 2.1.9 1.6.16, 2.1.9

References

CVSS score 3.7/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-200
Platform
Python (PyPI)
Package
nautobot
Disclosed
26.03.2024
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-1687 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-m732-wvh2-7cq4 - CC BY 4.0

Vulnerability history: nautobot

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (19) in the archive
Total entries
19
First → latest
02.2023 09.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 9
  • Medium 6
  • Low 4

Disclosures per year

  1. 2023: 5
  2. 2024: 5
  3. 2025: 2
  4. 2026: 7
Severity:
  1. High · 7.1 CVE-2026-44798 >= 3.0.0a2, < 3.1.2, < 2.4.33 3.1.2, 2.4.33
  2. High · 8.5 CVE-2026-44797 >= 3.0.0a2, < 3.1.2, < 2.4.33 3.1.2, 2.4.33
  3. High · 7.5 CVE-2024-34707 < 1.6.22, >= 2.0.0, < 2.2.4 1.6.22, 2.2.4
  4. High · 7.5 CVE-2024-32979 >= 1.5.0, < 1.6.20, >= 2.0.0, < 2.2.3 1.6.20, 2.2.3
  5. Unauthenticated views may expose information to anonymous users this entry
    Low · 3.7 CVE-2024-29199 < 1.6.16, >= 2.0.0, < 2.1.9 1.6.16, 2.1.9
  6. High · 7.1 CVE-2024-23345 >= 2.0.0, < 2.1.2, < 1.6.10 2.1.2, 1.6.10
  7. High · 7.1 CVE-2023-48705 < 1.6.6, >= 2.0.0, < 2.0.5 1.6.6, 2.0.5
  8. High · 7.7 CVE-2023-46128 >= 2.0.0, < 2.0.3 2.0.3

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.