https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-24T19:56:36.343484+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2020-51570 cnvd-2020-51570 2026-10-24T19:56:36.346746+00:00 cnvd-2020-51570 https://cve.radiocsirt.org/vuln/euvd-2026-36339 EUVD-2026-36339 2026-10-24T19:56:36.346779+00:00 EUVD-2026-36339 https://cve.radiocsirt.org/vuln/fkie_cve-2020-4045 fkie_cve-2020-4045 2026-10-24T19:56:36.346794+00:00

SSB-DB version 20.0.0 has an information disclosure vulnerability. The get() method is supposed to only decrypt messages when you explicitly ask it to, but there is a bug where it's decrypting any message that it can. This means that it is returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around get() to anonymous peers. This is fixed in version 20.0.1. Note that users of SSB-Server verion 16.0.0 should upgrade to 16.0.1 to get the fixed version of SSB-DB.

 https://cve.radiocsirt.org/vuln/ghsa-mpgr-2cx9-327h GHSA-mpgr-2cx9-327h — Information disclosure in SSB-DB 2026-10-24T19:56:36.346826+00:00

Affected: npm: ssb-db

### Impact _What kind of vulnerability is it? Who is impacted?_

Servers running SSB-DB 20.0.0 (which is packaged with SSB-Server 16.0.0) must upgrade immediately.

**There is no evidence that other SSB apps are vulnerable or that this problem has been exploited in the wild.**

The `get()` method is supposed to only decrypt messages when you explicitly ask it to, but there's a bug where it's decrypting any message that it can. This means that it's returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around `get()` to anonymous peers.

### Patches _Has the problem been patched? What versions should users upgrade to?_

Yes, please upgrade to SSB-DB 20.0.1 (or SSB-Server 16.0.1) immediately.

### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_

You may be able to disable the most obvious attack vector, SSB-OOO, by disabling the plugin, but you should upgrade immediately anyway.

### For more information

If you have any questions or comments about this advisory, open an issue in [SSB-DB](https://github.com/ssbc/ssb-db/)

 https://cve.radiocsirt.org/vuln/gsd-2020-4045 gsd-2020-4045 2026-10-24T19:56:36.346864+00:00 gsd-2020-4045