Is PrivateBin 1.3.5 patched?
Current stable (2.0.4): 100/100
1.3.5 has 1 open critical-or-high vulnerability. Run 1.4.0 or later to clear it. See what 1.4.0 fixes →
Summary iPlain-English security status for PrivateBin 1.3.5, built from its CVEs, active-exploitation data, end-of-life date and latest release.
PrivateBin 1.3.5 is part of the 1.3 release line. 1 known vulnerability affects it. The minimum safe version is 1.4.0 — upgrade to it or later to clear the open critical/high issues. The 1.3 line reached end-of-life on 2022-04-09, so it no longer receives security patches. The latest supported PrivateBin release is 2.0.4.
Known issues affecting 1.3.5
Exploited first, then by exploitation probability.
CVE-2022-24833 HIGH EPSS 1% → fixed in 1.4.0Other PrivateBin versions
Check another release line of PrivateBin.
Frequently asked
Is PrivateBin 1.3.5 patched?
PrivateBin 1.3.5 is end-of-life and no longer receives security patches. Move to 2.0.4.
What version should I upgrade PrivateBin 1.3.5 to?
Upgrade PrivateBin 1.3.5 to at least 1.4.0 to clear its 1 open critical-or-high vulnerability.
When does PrivateBin 1.3 reach end-of-life?
PrivateBin 1.3 reached end-of-life on 2022-04-09 and no longer receives security patches.
What is the latest version of PrivateBin?
The latest supported PrivateBin release is 2.0.4.
Is PrivateBin 1.3.5 still receiving security updates?
No — PrivateBin 1.3.5 is on the 1.3 line, which reached end-of-life on 2022-04-09 and no longer receives security updates. Upgrade to 2.0.4 or later to stay supported.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against PrivateBin's official advisory before you patch or upgrade — PrivateBin official site ↗