Miggo at BlackHat 2026!
Easily map the attack path and prioritize which CVEs are a threat to your organization
Miggo AIGenerate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| nautobot | pip | >= 3.0.0a2, < 3.1.2 | 3.1.2 |
| nautobot | pip | < 2.4.33 | 2.4.33 |
Miggo AIRoot Cause AnalysisThe vulnerability lies in the improper enforcement of permissions when handling GenericForeignKey relationships in Nautobot's REST API. The core issue is in the validate method of the ValidatedModelSerializer class, which is a base class for many serializers in the application. This method did not check if the user had 'view' permissions for the object being referenced by a GenericForeignKey. This allowed a user with permission to create or edit an object (like an ImageAttachment) to link it to another object (like a Device) that they were not supposed to have access to, as long as they knew its UUID.
The patch addresses this by adding a permission check within the ValidatedModelSerializer.validate method. It now uses the qs.restrict(user, 'view') method to filter the queryset of the related object, ensuring the user has the necessary permissions before the relationship is created.
A specific example of a vulnerable serializer was ImageAttachmentSerializer, which had its own validate method that also lacked this permission check. The fix for this serializer was to remove its custom validate method, so it would inherit the newly patched and secure validate method from ValidatedModelSerializer.
ValidatedModelSerializer.validatenautobot/core/api/serializers.py
ImageAttachmentSerializer.validatenautobot/extras/api/serializers.py