CVE-2026-44794

Workarounds

No known workarounds at this time.

References

• 2.4.33 (patch)
• 3.1.2 (patch)

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-44794 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.2, 2.4.33); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-44794? CVE-2026-44794 is a medium-severity missing authorization vulnerability in nautobot (pip), affecting versions >= 3.0.0a2, < 3.1.2. It is fixed in 3.1.2, 2.4.33. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-44794? CVE-2026-44794 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of nautobot are affected by CVE-2026-44794? nautobot (pip) versions >= 3.0.0a2, < 3.1.2 is affected.
4. Is there a fix for CVE-2026-44794? Yes. CVE-2026-44794 is fixed in 3.1.2, 2.4.33. Upgrade to this version or later.
5. Is CVE-2026-44794 exploitable, and should I be worried? Whether CVE-2026-44794 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44794 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44794?
   • Upgrade nautobot to 3.1.2 or later
   • Upgrade nautobot to 2.4.33 or later