Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@powersync/service-sync-rules

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5npmAmendedPublished

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

    CVE-2026-30870 · GHSA-q6wc-xx4m-92fj

    Affected
    • npm @powersync/service-sync-rules >= 0.32.0, <= 0.32.0
    Fixed in
    0.33.0· Vendor fix available
    Issue
    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 (bucketdefinitions) 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…

    Recommended action: Upgrade to 0.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →