https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T21:52:21.869665+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-parse-2020-15270 BIT-parse-2020-15270 — Improper session expiration in Parse Server 2026-10-04T21:52:21.873689+00:00

Affected: Bitnami: parse

Parse Server (npm package parse-server) broadcasts events to all clients without checking if the session token is valid. This allows clients with expired sessions to still receive subscription objects. It is not possible to create subscription objects with invalid session tokens. The issue is not patched.

 https://cve.radiocsirt.org/vuln/euvd-2026-42817 EUVD-2026-42817 2026-10-04T21:52:21.873756+00:00 EUVD-2026-42817 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15270 fkie_cve-2020-15270 2026-10-04T21:52:21.873778+00:00

Parse Server (npm package parse-server) broadcasts events to all clients without checking if the session token is valid. This allows clients with expired sessions to still receive subscription objects. It is not possible to create subscription objects with invalid session tokens. The issue is not patched.

 https://cve.radiocsirt.org/vuln/ghsa-2xm2-xj2q-qgpj GHSA-2xm2-xj2q-qgpj — receiving subscription objects with deleted session 2026-10-04T21:52:21.873812+00:00

Affected: npm: parse-server

Original Message: Hi,

I create objects with one client with an ACL of all users with a specific column value. Thats working so far.

Then I deleted the session object from one user to look if he can receive subscription objects and he can receive them. The client with the deleted session cant create new objects, which Parse restricts right.

The LiveQueryServer doesnt detect deleted sessions after the websocket connection was established. There should be a mechanism that checks in an specific interval if the session exists. I dont know if its true with expired sessions.

Any solutions?

Parse version: 4.3.0 Parse js SDK version: 2.17

Solution: Hi guys.

I've found and fixed the problem. It happens because there are two caches in place for the session token:

- at Parse Server level, which, according with the docs, should be changed via cacheTTL option and defaults to 5 seconds; - at Parse Live Query level, which, according with the docs, should be changed via liveQueryServerOptions.cacheTimeout and defaults to 30 days.

But there are three problems:

- cacheTTL has currently no effect over Live Query Server; - cacheTimeout also has currently no effect over Live Query Server; - cacheTimeout actually defaults to 1h.

So, currently, if you wait 1 hour after the session token was invalidated, the clients using the old session token are not able to receive the events.

What I did:

- Added a test case for the problem; - Fixed cacheTTL for Live Query Server; - Fixed cacheTimeout…

 https://cve.radiocsirt.org/vuln/gsd-2020-15270 gsd-2020-15270 2026-10-04T21:52:21.873881+00:00 gsd-2020-15270