CVE-2026-44794Medium· 5.4▾ SunlitNautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.7 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.2%
In the case of inter-object references via GenericForeignKey (a pattern allowing an object to reference another object that may belong to one of several different "content types" or database tables), when creating or updating an object containing a GenericForeignKey, Nautobot's REST API failed to enforce user "view" permissions when determining whether a given reference to another object would be valid.
As a concrete example, a user:
ImageAttachment recordsDevice recordsDevice that they do not otherwise have access tocould create via the REST API an ImageAttachment linked to that specific Device.
Other models that use GenericForeignKey and may be writable via the REST API, and hence have a similar vulnerability to ImageAttachment, may include:
ApprovalWorkflowCableConfigContextContactAssociationDataComplianceDeviceExportTemplateGraphQLQueryNoteObjectMetadataRelationshipAssociationStaticGroupAssociationVirtualMachineAdditionally, any Nautobot Apps that provide models with a REST API and use GenericForeignKey may have a similar vulnerability for their models.
A general-purpose fix has been implemented in Nautobot 2.4.33 and 3.1.2, which ensures correct application of "view" permissions when creating or modifying object references via GenericForeignKey throughout the REST API. Individual models/views/serializers generally will not require any specific code changes to benefit from this fix.
No known workarounds at this time.
nautobot >= 3.0.0a2, < 3.1.2nautobot < 2.4.33Upgrade to a patched release:
nautobot 3.1.2nautobot 2.4.33Connected by shared product, vendor, weakness, or advisory.
CVE-2026-44796Medium· 6.5Nautobot: Object bulk rename UI actions vulnerable to denial of service by crafted regular expression (REDoS)
CVE-2026-44798High· 7.1Nautobot: GitRepository.current_head field should not be writable through REST API
CVE-2026-44797High· 8.5Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
CVE-2026-83801Medium· 5.4Nautobot is a Network Source of Truth and Network Automation Platform
CVE-2026-83805Medium· 6.4Nautobot is a Network Source of Truth and Network Automation Platform
CVE-2024-23345High· 7.1XSS potential in rendered Markdown fields (comments, description, notes, etc.)