CVE-2026-59093 Weaviate Vulnerability
Weaviate before 1.38.0 does not verify that a principal performing an RBAC role assignment holds the permissions granted by the assigned role. The assignRoleToUser and assignRoleToGroup handlers (POST /authz/users/{id}/assign and /authz/groups/{id}/assign) authorize only that the caller may assign roles to the target user or group, not the permissions contained in the assigned roles, unlike role creation which enforces that a user can only create roles with permissions less than or equal to its own. A user holding only the delegated assign_and_revoke_users or assign_and_revoke_groups permission can assign the built-in admin role, or any high-privilege custom role, to itself or others, escalating to full administrative control of the database.
Quick answer
Weaviate should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Weaviate before 1.38.0
Fixed versions
- Weaviate 1.38.0 or later
How to fix it
CVE-2026-59093 affects Weaviate. The affected range is Weaviate before 1.38.0. Update to Weaviate 1.38.0 or later. Fix exposed systems first, especially where internet-facing services, admin panels, and trusted internal users can be reached. If abuse is suspected, review logs and rotate secrets that may have been exposed.
- Inventory every Weaviate install and note the exact version.
- Compare each install with the affected range: Weaviate before 1.38.0.
- Update to Weaviate 1.38.0 or later.
- If you cannot patch today, restrict internet-facing services, admin panels, and trusted internal users to trusted users and networks.
- Back up the current configuration before changing production systems.
- Review recent logs for crashes, strange admin actions, failed logins, or unexpected access.
- Rotate passwords, tokens, certificates, or keys if compromise is suspected.
- Document the change, owner, date, and final version.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version now matches the fixed guidance: Weaviate 1.38.0 or later.
- Confirm old affected versions are no longer deployed: Weaviate before 1.38.0.
- Confirm internet-facing services, admin panels, and trusted internal users is limited to the smallest needed group.
- Rerun the relevant Fixnx scan or internal security check after the change.
- Save logs, screenshots, or package output as proof of the fix.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59093?
Weaviate versions listed as affected should be reviewed: Weaviate before 1.38.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.