PYSEC-2026-1687
Vulnerability from pysec - Published: 2026-07-07 11:45 - Updated: 2026-07-07 17:24Impact
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?
| Name | purl | nautobot | pkg:pypi/nautobot |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "nautobot",
"purl": "pkg:pypi/nautobot"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.6.16"
},
{
"introduced": "2.0.0"
},
{
"fixed": "2.1.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0",
"1.0.0a1",
"1.0.0a2",
"1.0.0b1",
"1.0.0b2",
"1.0.0b3",
"1.0.0b4",
"1.0.1",
"1.0.2",
"1.0.3",
"1.1.0",
"1.1.1",
"1.1.2",
"1.1.3",
"1.1.4",
"1.1.5",
"1.1.6",
"1.2.0",
"1.2.1",
"1.2.10",
"1.2.11",
"1.2.2",
"1.2.3",
"1.2.4",
"1.2.5",
"1.2.6",
"1.2.7",
"1.2.8",
"1.2.9",
"1.3.0",
"1.3.1",
"1.3.10",
"1.3.2",
"1.3.3",
"1.3.4",
"1.3.5",
"1.3.6",
"1.3.7",
"1.3.8",
"1.3.9",
"1.4.0",
"1.4.1",
"1.4.10",
"1.4.2",
"1.4.3",
"1.4.4",
"1.4.5",
"1.4.7",
"1.4.8",
"1.4.9",
"1.5.0",
"1.5.1",
"1.5.10",
"1.5.11",
"1.5.12",
"1.5.13",
"1.5.14",
"1.5.15",
"1.5.16",
"1.5.17",
"1.5.18",
"1.5.19",
"1.5.2",
"1.5.20",
"1.5.21",
"1.5.22",
"1.5.23",
"1.5.24",
"1.5.3",
"1.5.4",
"1.5.5",
"1.5.6",
"1.5.7",
"1.5.8",
"1.5.9",
"1.6.0",
"1.6.1",
"1.6.10",
"1.6.11",
"1.6.12",
"1.6.13",
"1.6.14",
"1.6.15",
"1.6.2",
"1.6.3",
"1.6.4",
"1.6.5",
"1.6.6",
"1.6.7",
"1.6.8",
"1.6.9",
"2.0.0",
"2.0.1",
"2.0.2",
"2.0.3",
"2.0.4",
"2.0.5",
"2.0.6",
"2.1.0",
"2.1.0b1",
"2.1.1",
"2.1.2",
"2.1.3",
"2.1.4",
"2.1.5",
"2.1.6",
"2.1.7",
"2.1.8"
]
}
],
"aliases": [
"CVE-2024-29199",
"GHSA-m732-wvh2-7cq4"
],
"details": "### Impact\n\nA number of Nautobot URL endpoints were found to be improperly accessible to unauthenticated (anonymous) users, including the following:\n\n- `/api/graphql/` (1)\n- `/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)\n- `/dcim/racks/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n- `/dcim/devices/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n- `/extras/job-results/\u003cuuid:pk\u003e/log-table/`\n- `/extras/secrets/provider/\u003cstr:provider_slug\u003e/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)\n- `/ipam/prefixes/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n- `/ipam/ip-addresses/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n- `/virtualization/clusters/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n- `/virtualization/virtual-machines/\u003cuuid:pk\u003e/dynamic-groups/` (1)\n\n(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.\n\nOf 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/\u003cuuid:pk\u003e/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.\n\nIn 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). \n\n- `/api/`\n- `/api/circuits/`\n- `/api/dcim/`\n- `/api/extras/`\n- `/api/ipam/`\n- `/api/plugins/`\n- `/api/tenancy/`\n- `/api/users/`\n- `/api/virtualization/`\n\nAll 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.\n\n### Patches\n\nFixes will be included in Nautobot 1.6.16 and 2.1.9.\n\n### Workarounds\n\nPartial 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.\n\n### References\n_Are there any links users can visit to find out more?_\n",
"id": "PYSEC-2026-1687",
"modified": "2026-07-07T17:24:47.598418Z",
"published": "2026-07-07T11:45:36.512992Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/security/advisories/GHSA-m732-wvh2-7cq4"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29199"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/pull/5464"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/pull/5465"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/commit/2fd95c365f8477b26e06d60b999ddd36882d5750"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/commit/dd623e6c3307f48b6357fcc91925bcad5192abfb"
},
{
"type": "PACKAGE",
"url": "https://github.com/nautobot/nautobot"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/releases/tag/v1.6.16"
},
{
"type": "WEB",
"url": "https://github.com/nautobot/nautobot/releases/tag/v2.1.9"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/nautobot"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-m732-wvh2-7cq4"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Unauthenticated views may expose information to anonymous users"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.