Synced 03 Aug 2026 05:54 UTC Account
← Piwigo

Piwigo vulnerabilities: known CVEs & security history

Piwigo · Media / Gallery · 6 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Piwigo release lines — 6 in total. A CVE here doesn't mean your version is affected — check Piwigo's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known Piwigo CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-27634 critical 9.8 1% 2026
CVE-2026-27833 high 7.5 2% 2026
CVE-2026-27885 high 7.2 0% 2026
CVE-2026-27834 high 7.2 0% 2026
CVE-2024-46605 medium 6.1 0% 2024
CVE-2024-46606 medium 5.4 0% 2024

Is my Piwigo version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Piwigo version → · Monitor Piwigo for new CVEs →

Piwigo vulnerabilities — frequently asked

How many known vulnerabilities does Piwigo have?

IsItPatched tracks 6 CVEs for Piwigo. 1 is critical-severity and 3 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Piwigo have any actively-exploited vulnerabilities?

None of Piwigo's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Piwigo vulnerability?

Among tracked issues, CVE-2026-27634 (CRITICAL, CVSS 9.8) ranks highest — a SQL injection weakness.

Is Piwigo safe to use?

It depends on the version. The latest supported Piwigo release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Piwigo security status · Piwigo end-of-life · actively-exploited CVEs. Always verify against Piwigo's advisories — see our disclaimer.