Summary iPlain-English security verdict for Piwigo, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Piwigo currently scores 55/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
Disclosure trend iNew CVEs published for Piwigo each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2026-27634 CRITICAL SQL injection EPSS 1% → fixed in 16.3.0Get alerted about Piwigo
Be emailed the moment Piwigo gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Piwigo — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Piwigo safe and patched?
Piwigo currently scores 55/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
What should I do about Piwigo now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Piwigo's official advisory.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Piwigo's official advisory before you patch or upgrade — Piwigo official site ↗