Skip to content

Security policy 🛡️🏴‍☠️

Report vulnerabilities privately using the process below. Keep credentials and sensitive deployment details out of public reports.

Supported versions ⚓

Security fixes target the current main branch. Older local copies and modified PIA scripts are not maintained here.

Version Supported
main branch ✅
Older local copies ❌
Forked or modified PIA scripts ❌

Important

Plundarr consumes the published Privateerr image for PIA WireGuard config and port-forwarding metadata. Privateerr uses upstream PIA manual connection scripts, and issues in those scripts should also be reported to the PIA project.

Report a vulnerability 🦜

Please do not open a public GitHub issue for secrets, credential leaks, auth bypasses, or details that could expose users to attacks.

Report vulnerabilities using GitHub's private vulnerability reporting form. To find it from the repository:

  1. Go to the repository's Security tab.
  2. Choose Report a vulnerability.
  3. Include clear steps to reproduce, affected files, logs, image tags, and any relevant Docker Compose settings.

Do not send vulnerability details through Discord, discussions, issues, or pull requests. Those routes are for non-sensitive support and public collaboration.

If private vulnerability reporting is unavailable, open a GitHub issue containing only a brief, non-sensitive request for a private reporting channel. Do not describe the vulnerability publicly.

Include useful evidence 📜

Helpful reports include:

  • What you found.
  • How to reproduce it.
  • What branch, image tag, or commit ye tested.
  • Whether it affects Plundarr Compose wiring, PIA WireGuard, port forwarding, Privateerr integration, Gluetun integration, or another service.
  • Any safe logs with secrets removed.

Warning

Never include real usernames, passwords, WireGuard private keys, generated wg0.conf files, forwarded ports, or live privateerr.env metadata in a public report.

Understand response expectations 🕰️

Maintenance is best effort. I aim to:

  • Acknowledge valid private reports within 7 days.
  • Triage severity and scope as soon as possible.
  • Patch accepted issues in main.
  • Credit reporters when requested and safe to do so.

If a report is declined, I will explain the reason privately where practical.

Understand stack security 🔎

Plundarr pulls published container images for the stack and keeps configuration in service-specific directories. Pull updated stable images regularly so accepted security fixes reach the deployment.

Image scan evidence

The container scan review retains dated artifact identities, unresolved findings, the CVE-2026-78661-only Compose exception, and reproduction commands. Read its scope before applying results to a moving image tag. A passing CI exception is not a clean artifact scan.

Use the support guide for non-sensitive setup questions and reproducible bugs.

Keep sensitive information private throughout reporting and recovery.