GHSA-m732-wvh2-7cq4
LOWUnauthenticated views may expose information to anonymous users
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
nautobot🐍nautobotReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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-variableortext-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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | nautobot | all versions | 1.6.16 |
| 🐍PyPI | nautobot | ≥ 2.0.0&&< 2.1.9 | 2.1.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nautobot. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nautobot to 1.6.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m732-wvh2-7cq4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m732-wvh2-7cq4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-m732-wvh2-7cq4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m732-wvh2-7cq4 in your dependencies?
O3 detects GHSA-m732-wvh2-7cq4 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.