Details
- Read via forged
meta.knowledgeon model create, through the built-inview_filetool: @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}) viahas_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.