CVE-2026-51916: High severity transformeroptimus superagi vulnerability

Published Oct 2, 2026

Updated

TransformerOptimus SuperAGI v0.0.14 contains an incorrect access control vulnerability in deleteuserknowledge in superagi/controllers/knowledges.py. In affected source snapshots, POST /knowledges/delete/{knowledgeid} deletes the selected knowledge object without requiring authentication in the route and without verifying organization ownership of the supplied knowledgeid.

Affected Software

1 affected component

transformeroptimus superagi=0.0.14

Event History

Oct 2, 2026

CVE Published

via MITRE·12:00 AM

Data Sourced

via MITRE·12:00 AM

Description

Data Sourced

via NVD·04:16 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any network-reachable, unauthenticated attacker can send a POST request to the affected deletion endpoint. No credentials or user interaction are required.

What data can an attacker delete?

An attacker who knows or can supply a knowledge_id can delete the corresponding knowledge object. The affected route does not verify that the object belongs to an authorized organization.

Are default deployments affected?

Affected source snapshots of TransformerOptimus SuperAGI v0.0.14 are affected because the route does not require authentication. Exposure depends on whether the application endpoint is network reachable.

What can be done if patching is not immediately possible?

Restrict network access to the application and prevent untrusted users from reaching POST /knowledges/delete/{knowledge_id}. This reduces exposure to unauthenticated deletion requests.

CVE-2026-51916: High severity transformeroptimus superagi vulnerability

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What data can an attacker delete?

Are default deployments affected?

What can be done if patching is not immediately possible?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What data can an attacker delete?

Are default deployments affected?

What can be done if patching is not immediately possible?