# CVE-2026-65314: ElectricSQL Electric Postgres Sync information disclosure via subset where clauses

Source: https://junglewise.ai/threats/cve-2026-65314-electricsql-electric-postgres-sync-information-disclosure-via  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-21. Updated: 2026-07-22  
License: CC BY 4.0 with a link back

CVE-2026-65314 · Severity: medium · CVSS 4.3 · Published 2026-07-21

Electric Postgres Sync, a tool used to synchronize data between PostgreSQL databases and client applications, contains a flaw that could allow unauthorized users to see sensitive information. By sending specific database queries, an attacker can figure out the contents of data columns they are not supposed to see, even if those columns were intentionally hidden. This could lead to the exposure of private customer data or internal business records that were meant to be restricted.

## Quick answers

**Is CVE-2026-65314 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-65314 being exploited in the wild.

**How severe is CVE-2026-65314?** Medium severity, with a CVSS score of 4.3, published 21 July 2026.

**Which products and versions are affected?** ElectricSQL Electric < 1.6.10.

**Is there a fix for CVE-2026-65314?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-65314 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-65314?** Check whether you run ElectricSQL Electric at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An information disclosure vulnerability exists in Electric Postgres Sync (specifically the sync-service) due to an observable discrepancy when processing 'subset where' clauses. The 'columns' parameter, which was previously documented as a way to restrict access to sensitive fields, only controls which columns are returned in the response but does not prevent those columns from being evaluated in query logic. An authenticated attacker can craft specific 'where' conditions against excluded columns and observe whether rows are returned to iteratively deduce the sensitive values. The issue is addressed in version 1.6.10 by the introduction of a new 'queryable_columns' parameter to explicitly define which fields are accessible for query logic.

## Affected products

- ElectricSQL Electric Postgres Sync < 1.6.10

## Timeline

- 2026-06-10: advisory: GitHub Security Advisory published
- 2026-07-21: disclosed: NVD publication date

## References

- [https://github.com/electric-sql/electric](https://github.com/electric-sql/electric)
- [https://github.com/electric-sql/electric/security/advisories/GHSA-c82q-v86f-c87f](https://github.com/electric-sql/electric/security/advisories/GHSA-c82q-v86f-c87f)
- [https://www.vulncheck.com/advisories/electric-postgres-sync-excluded-column-value-inference-via-subset-where-clauses](https://www.vulncheck.com/advisories/electric-postgres-sync-excluded-column-value-inference-via-subset-where-clauses)

## Related threats

- [ElectricSQL SQL injection in /v1/shape API order_by parameter](https://junglewise.ai/threats/cve-2026-40906-electricsql-sql-injection-in-v1-shape-api-order-by-parameter)