CVE-2026-44794: Nautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
Impact
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:
- who has permission to create or update ImageAttachment records - but who lacks permission to view (some or all) Device records - but who knows (via some other mechanism) the UUID of a specific Device that they do not otherwise have access to
could 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:
- ApprovalWorkflow - Cable - ConfigContext - ContactAssociation - DataCompliance - Device - ExportTemplate - GraphQLQuery - Note - ObjectMetadata - RelationshipAssociation - StaticGroupAssociation - VirtualMachine
Additionally, any Nautobot Apps that provide models with a REST API and use GenericForeignKey may have a similar vulnerability for their models.
Patches
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.
Workarounds
No known workarounds at this time.
References
- 2.4.33 (<a href="https://github.com/nautobot/nautobot/commit/9918bdb9bcf1eb42cda72c344f420a64ef7665f1">patch</a>) - 3.1.2 (<a href="https://github.com/nautobot/nautobot/commit/36cde7148a207234de6212ec074f321dbc9d1b5b">patch</a>)
Other sources
Nautobot is a Network Source of Truth and Network Automation Platform. Prior to 2.4.33 and 3.1.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. This vulnerability is fixed in 2.4.33 and 3.1.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/nautobotto a version that resolves this vulnerability.Fixed in 2.4.33 - Upgrade
Upgrade
pip/nautobotto a version that resolves this vulnerability.Fixed in 3.1.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44794?
CVE-2026-44794 has a high severity level due to the potential for unauthorized data manipulation via GenericForeignKey.
How do I fix CVE-2026-44794?
To fix CVE-2026-44794, upgrade Nautobot to version 2.4.33 or 3.1.2 or later.
What software is affected by CVE-2026-44794?
CVE-2026-44794 affects Nautobot versions up to 2.4.33 and between 3.0.0a2 to 3.1.2.
What is the impact of CVE-2026-44794 on Nautobot?
CVE-2026-44794 can lead to incorrect handling of object references, potentially resulting in data integrity issues.
Is there a workaround for CVE-2026-44794?
There are no known workarounds for CVE-2026-44794; the recommended approach is to apply the necessary updates.