Skip to content

Commit 5a39243

Browse files
1 parent e37f0f2 commit 5a39243

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

advisories/github-reviewed/2026/03/GHSA-q6wc-xx4m-92fj/GHSA-q6wc-xx4m-92fj.json

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-q6wc-xx4m-92fj",
4-
"modified": "2026-03-10T18:43:23Z",
4+
"modified": "2026-03-23T17:29:15Z",
55
"published": "2026-03-07T02:23:24Z",
66
"aliases": [
77
"CVE-2026-30870"
88
],
99
"summary": "PowerSync: Some sync filters ignored on 1.20.0 using `config.edition: 3`",
10-
"details": "### Impact\n\nIn version **1.20.0**, when using new sync streams with `config.edition: 3`, certain subquery filters were ignored when determining which data to sync to users.\n\nDepending on the sync stream configuration, this could result in authenticated users syncing data that should have been restricted.\n\nOnly queries that gate synchronization using subqueries without partitioning the result set are affected.\n\nNot affected:\n * Sync rules (bucket_definitions)\n * Sync streams using `config.edition: 2`\n * No data is exposed without authenticating\n\n### Patches\n\nThe issue is **fixed in 1.20.1**. Restarting the service with the new version is sufficient - no reprocessing of sync streams is required.\n\nAny data that users erroneously synced will be automatically removed from those devices when they connect again.\n\nPowerSync has updated all affected PowerSync Cloud instances to the fixed version, and is reaching out to affected customers.\n\nFor self-hosted PowerSync instances, update to the latest version and restart.\n\n### Affected queries\n\nSubqueries used only to determine whether or not a table should be synced (without partitioning the data itself) are affected. Examples:\n\n```sql\n-- Goal: Sync a table only to admin users\n-- 1.20.0: all authenticated users would sync this table\nSELECT * FROM sensitive_table WHERE auth.user_id() IN (SELECT user_id FROM admins)\nSELECT * FROM sensitive_table WHERE 1 IN (SELECT 1 FROM users WHERE id = auth.user_id() AND is_admin = TRUE)\n\n-- Goal: Sync a table only if authorized\n-- 1.20.0: all authenticated users would sync this table\nSELECT * FROM sensitive_table WHERE 'sensitive_table' IN (SELECT table_name FROM synced_table WHERE \"user\" = auth.user_id())\nSELECT * FROM sensitive_table WHERE 'sensitive_table' IN auth.parameter('allowed_tables')\n```\n\nQueries that partition data (for example `SELECT * FROM sensitive_table WHERE owner IN (SELECT id FROM users WHERE is_admin AND id = auth.user_id())`) are not affected by this issue.",
10+
"details": "### Impact\n\nIn version **1.20.0**, when using new sync streams with `config.edition: 3`, certain subquery filters were ignored when determining which data to sync to users.\n\nDepending on the sync stream configuration, this could result in authenticated users syncing data that should have been restricted.\n\nOnly queries that gate synchronization using subqueries without partitioning the result set are affected.\n\nNot affected:\n * Sync rules (bucket_definitions)\n * Sync streams using `config.edition: 2`\n * No data is exposed without authenticating\n\n### Patches\n\nThe issue is **fixed in 1.20.1**. Restarting the service with the new version is sufficient - no reprocessing of sync streams is required.\n\nAny data that users erroneously synced will be automatically removed from those devices when they connect again.\n\nWe have updated all affected PowerSync Cloud instances to the fixed version, and are reaching out to affected customers.\n\nFor self-hosted PowerSync instances, update to the latest version and restart.\n\n### Affected queries\n\nSubqueries used only to determine whether or not a table should be synced (without partitioning the data itself) are affected. Examples:\n\n```sql\n-- Goal: Sync a table only to admin users\n-- 1.20.0: all authenticated users would sync this table\nSELECT * FROM sensitive_table WHERE auth.user_id() IN (SELECT user_id FROM admins)\nSELECT * FROM sensitive_table WHERE 1 IN (SELECT 1 FROM users WHERE id = auth.user_id() AND is_admin = TRUE)\n\n-- Goal: Sync a table only if authorized\n-- 1.20.0: all authenticated users would sync this table\nSELECT * FROM sensitive_table WHERE 'sensitive_table' IN (SELECT table_name FROM synced_table WHERE \"user\" = auth.user_id())\nSELECT * FROM sensitive_table WHERE 'sensitive_table' IN auth.parameter('allowed_tables')\n```\n\nQueries that partition data (for example `SELECT * FROM sensitive_table WHERE owner IN (SELECT id FROM users WHERE is_admin AND id = auth.user_id())`) are not affected by this issue.",
1111
"severity": [
1212
{
1313
"type": "CVSS_V3",
@@ -25,17 +25,17 @@
2525
"type": "ECOSYSTEM",
2626
"events": [
2727
{
28-
"introduced": "0"
28+
"introduced": "1.20.0"
2929
},
3030
{
3131
"fixed": "1.20.1"
3232
}
3333
]
3434
}
3535
],
36-
"database_specific": {
37-
"last_known_affected_version_range": "<= 1.20.0"
38-
}
36+
"versions": [
37+
"1.20.0"
38+
]
3939
},
4040
{
4141
"package": {
@@ -47,17 +47,17 @@
4747
"type": "ECOSYSTEM",
4848
"events": [
4949
{
50-
"introduced": "0"
50+
"introduced": "0.32.0"
5151
},
5252
{
5353
"fixed": "0.33.0"
5454
}
5555
]
5656
}
5757
],
58-
"database_specific": {
59-
"last_known_affected_version_range": "<= 0.32.0"
60-
}
58+
"versions": [
59+
"0.32.0"
60+
]
6161
}
6262
],
6363
"references": [

0 commit comments

Comments
 (0)