Advisory

PYSEC-2026-2761

Details, part 3 of 3. The advisory

Details

  • Read via forged meta.knowledge on model create, through the built-in view_file tool: @0xEr3n (earliest filing).
  • Distinct paths demonstrated by @5yu4n: the import endpoint (POST /api/v1/models/import), and cross-user read and deletion through the file API (GET / DELETE /api/v1/files/{id}) via has_access_to_file()'s model branch.

Fix validates meta.knowledge ownership on create, update, and import; blocking the forged entry closes both read and delete. One CVE for the consolidated advisory.

Sources & licences