Skip to content

PowerSync: Some sync filters ignored on 1.20.0 using `config.edition: 3`

Moderate severity GitHub Reviewed Published Mar 6, 2026 in powersync-ja/powersync-service • Updated Mar 23, 2026

Package

npm @powersync/service-core (npm)

Affected versions

= 1.20.0

Patched versions

1.20.1
npm @powersync/service-sync-rules (npm)
= 0.32.0
0.33.0

Description

Impact

In 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.

Depending on the sync stream configuration, this could result in authenticated users syncing data that should have been restricted.

Only queries that gate synchronization using subqueries without partitioning the result set are affected.

Not affected:

  • Sync rules (bucket_definitions)
  • Sync streams using config.edition: 2
  • No data is exposed without authenticating

Patches

The issue is fixed in 1.20.1. Restarting the service with the new version is sufficient - no reprocessing of sync streams is required.

Any data that users erroneously synced will be automatically removed from those devices when they connect again.

We have updated all affected PowerSync Cloud instances to the fixed version, and are reaching out to affected customers.

For self-hosted PowerSync instances, update to the latest version and restart.

Affected queries

Subqueries used only to determine whether or not a table should be synced (without partitioning the data itself) are affected. Examples:

-- Goal: Sync a table only to admin users
-- 1.20.0: all authenticated users would sync this table
SELECT * FROM sensitive_table WHERE auth.user_id() IN (SELECT user_id FROM admins)
SELECT * FROM sensitive_table WHERE 1 IN (SELECT 1 FROM users WHERE id = auth.user_id() AND is_admin = TRUE)

-- Goal: Sync a table only if authorized
-- 1.20.0: all authenticated users would sync this table
SELECT * FROM sensitive_table WHERE 'sensitive_table' IN (SELECT table_name FROM synced_table WHERE "user" = auth.user_id())
SELECT * FROM sensitive_table WHERE 'sensitive_table' IN auth.parameter('allowed_tables')

Queries 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.

References

Published to the GitHub Advisory Database Mar 7, 2026
Reviewed Mar 7, 2026
Published by the National Vulnerability Database Mar 10, 2026
Last updated Mar 23, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

Improper Authorization

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

CVE ID

CVE-2026-30870

GHSA ID

GHSA-q6wc-xx4m-92fj

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.