https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T14:41:39.026882+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-341644 EUVD-2026-341644 2026-10-06T14:41:39.029398+00:00 EUVD-2026-341644 https://cve.radiocsirt.org/vuln/fkie_cve-2023-54366 fkie_cve-2023-54366 2026-10-06T14:41:39.029428+00:00

SurrealDB before 1.0.1 sets default table permissions to FULL instead of NONE, allowing SELECT, CREATE, UPDATE, and DELETE operations on tables without explicit permissions. Attackers with database access or unauthenticated users on publicly exposed instances can perform unrestricted operations on unprotected tables within their authorization scope.

 https://cve.radiocsirt.org/vuln/ghsa-x5fr-7hhj-34j3 GHSA-x5fr-7hhj-34j3 — SurrealDB: Full Table Permissions by Default 2026-10-06T14:41:39.029457+00:00

Affected: crates.io: surrealdb

Default table permissions in SurrealDB were `FULL` instead of `NONE`. This would lead to tables having `FULL` permissions for `SELECT`, `CREATE`, `UPDATE` and `DELETE` unless some other permissions were specified via the `PERMISSIONS` clause.

We have decided to treat this behaviour as a vulnerability due to its security implications, especially considering the lack of specific documentation and potential for confusion due to the `INFO FOR DB` statement previously not displaying default permissions. Treating it as a bug fix provides justification for a change in default behavior outside of a major release.

### Impact

Any client authorized to query data in a SurrealDB instance will have full access to any tables that were defined with no explicit permissions and that are within its authorization scope (i.e. namespace or database), including creating, reading, updating and deleting data. This is specially relevant for SurrealDB instances allowing guest access with publicly exposed interfaces (e.g. HTTP REST API or WebSocket API), since a remote unauthenticated user may gain full access to any tables that were defined without any explicit permissions. Tables that were defined with explicit permissions using the `PERMISSIONS` clause are not affected.

### Patches

- Version `1.0.1` includes a patch for this specific issue. Later releases will also include the patch. - Version `1.1.0-beta.1` and latest nightly releases already include the patch for this issue.

In patched versi…

 https://cve.radiocsirt.org/vuln/pysec-2026-3718 PYSEC-2026-3718 2026-10-06T14:41:39.029500+00:00

Affected: PyPI: surrealdb

SurrealDB before 1.0.1 sets default table permissions to FULL instead of NONE, allowing SELECT, CREATE, UPDATE, and DELETE operations on tables without explicit permissions. Attackers with database access or unauthenticated users on publicly exposed instances can perform unrestricted operations on unprotected tables within their authorization scope.