Password Pusher: November 2026

Password Pusher: November 2026
Security Fix, Prometheus Metrics, Color Skins & More
It's been five weeks since the October newsletter. A security fix to update for, a new Prometheus metrics endpoint, workspace availability policies on pwpush.com, updated legal documents and a new subprocessor, two Self-Hosted Pro releases, and a cluster of reliability improvements across the board. Let's get to it.
OSS Password Pusher
🔒 Security Fix
Update to at least v2.14.3. A sign-in throttle bypass allowed an attacker to avoid per-user login rate limits, making accounts with weak passwords more vulnerable to brute-force than the throttle intended. The bypass is now closed. This affects all self-hosted deployments running an older build.
Thanks to @nullbenny for the responsible disclosure.
📊 New: Prometheus Metrics
Self-hosted operators can now scrape Password Pusher directly with Prometheus. v2.16.0 adds a /metrics endpoint that exposes push and request counts, background job queue depth, and processing latency. If you run a Prometheus or Grafana stack, you get proper alerting on throughput changes and queue backlogs — no custom log parsing scripts required.
Full setup guide: Prometheus Metrics for OSS Password Pusher
Thanks to @cgrard for the idea and initial work.
🛡️ Proxy Hardening
Deployments behind reverse proxies now resolve client IPs correctly and consistently — across rate limiting and audit logs. Three releases address the same root issue: clients could forge their apparent IP by injecting a Forwarded header before it reached the proxy, causing rate limiters and audit log entries to record a spoofed address instead of the real one.
- v2.16.0 — ignore the client-controlled
Forwardedheader entirely; trust only proxy-setX-Forwarded-*headers - v2.16.2 —
PWP__TRUSTED_PROXIESnow accepts CIDR ranges, not just exact IPs (thanks @rennf93) - v2.17.0 — IPv4-mapped addresses are now trusted correctly through the same chain
If you run Password Pusher behind Caddy, nginx, Traefik, or any other reverse proxy, update to v2.17.0 or later.
📋 Other Highlights: v2.14.2 through v2.17.2
- GDPR/privacy fix (v2.15.1) — Some Bootstrap color themes were loading fonts from remote CDNs. All theme fonts are now packaged locally, so your instance makes no external requests at render time. Thanks to @OXERY for surfacing this.
- Data Explorer (v2.17.0) — Each push row now has a direct link to its full audit log. No more navigating away to find access history for a specific secret.
- SMTP implicit TLS (v2.17.0) — New
smtp_sslconfiguration flag for port 465 setups, alongside the existing STARTTLS support. - Passphrase generator (v2.15.0) — Clear and copy controls added to the generator UI.
- New one-click deploy platforms — Hostinger, Pethost, ZopDay, and Railyard added to the README. Thanks to @sadfun, @muskanbandta23, and @almokhtarbr for the contributions.
As always, dependency and security updates ship in every release cycle. The latest is v2.17.2.
New on pwpush.com
🔧 Workspace Availability Policies
Team and Organization workspace admins can now control which features are available to their users from Policy Settings. Two new availability controls ship in this update:
- Requests — disable the Requests feature entirely for your workspace. When off, the dashboard hides it, creation pages are removed, and the API v2 endpoint rejects new requests. Existing requests in the database are unaffected.
- Push kinds — enable or disable text, file, URL, and QR pushes independently. Quick Create and the creation tabs update automatically to reflect your policy; API v2 blocks creation of any disabled kind. Existing secret links for a disabled kind remain accessible — they're not deleted.
Configure both under Workspace → Policy → Pushes → Availability and Workspace → Policy → Requests → Availability.
This is available on Team and Organization plans on pwpush.com. Self-Hosted Pro admins continue to manage these settings globally through the Administration Center as before.
⚙️ Policy Settings UX
The Policy Expiration & Limits pages for Pushes and Requests have been merged into a single page. The settings are unchanged — the consolidation makes the policy area easier to navigate as it continues to grow.
🔐 SSO Security Fix
OmniAuth callback host validation has been hardened. A gap in how callback hosts were validated for SSO sign-in flows has been closed. No action needed by users.
⚖️ Updated Legal Documents & New Subprocessor
The Terms of Service, Privacy Policy, DPA, and cookie policy have all been updated in November 2026. Key changes:
- Who you contract with — Apnotic, LLC is explicitly stated as the sole contracting party for all customers worldwide, including EU, UK, and Switzerland.
- Self-hosted licensing — the Terms now clearly cover the Self-Hosted Pro licensing relationship and distinguish it from the hosted service.
- Privacy and DPA — wording aligned with actual hosted-service behaviour; the cookie policy updated to match.
ChartMogul has been added as a new subprocessor. Password Pusher now uses ChartMogul for subscription analytics and revenue metrics. Details:
- Entity: ChartMogul GmbH & Co. KG (Berlin, Germany)
- Infrastructure: AWS EU Ireland
- Data: Billing and subscription data synced from Stripe — customer names, emails, plan details. Does not handle push or request payload data.
- Certifications: SOC 2 Type II, GDPR compliant
The updated subprocessor list (now six total) is at pwpush.com/gdpr.
Self-Hosted Pro
🎨 v1.8.0 — Color Skins & Rebuilt Forms
v1.8.0 ships the color skin support previewed last month, plus a rebuilt push and request creation experience for all editions. Admins choose a skin from the Administration Center and all UI surfaces update to match — buttons, navigation, and inputs — while each user keeps their own light or dark mode preference independently.
The push and request creation forms have also been rebuilt, improving layout consistency and resolving several issues that had accumulated across the UI.
Blog post: Self-Hosted Pro v1.8.0 — Color Skins, Rebuilt Forms, and More
🔧 v1.9.0 — Puma-Embedded Worker & Audit Log Improvements
v1.9.0 eliminates the separate background worker process and fixes two audit log gaps. SolidQueue now runs inside the Puma web process rather than as a separate OS process — fewer moving parts to monitor and configure in production.
Two audit log improvements ship in the same release: user agents are now recorded on push and request access events, and the IP spoofing fix from the OSS releases applies here as well — the audit log records the same proxy-resolved IP that rate limiting uses.
Blog post: Self-Hosted Pro v1.9.0 — Puma-Embedded Worker, Audit Log Improvements, and Security Hardening
A Note on Bitwarden
Bitwarden changed its application license in October. Official builds — browser extensions, desktop apps, and direct downloads from bitwarden.com — now ship under the Bitwarden License v1.0, a commercial license that restricts redistribution and competing use. The source code is still published, but it no longer qualifies as open source under the OSI definition.
If this is relevant to how your team evaluates secure-sharing tools, our comparison page covers the differences in detail: pwpush.com/compare/bitwarden-send
📰 New on the Blog
Four posts since the last newsletter:
- Secrets Don't Belong in URLs — the Grok Build incident exposed 35,000 AI apps through passive DNS enumeration, but the deeper problem is using URLs as access control at all. Why ephemeral design changes the threat model.
- Prometheus Metrics for OSS Password Pusher — setup guide and configuration reference for the new
/metricsendpoint - Self-Hosted Pro v1.9.0 — Puma-Embedded Worker, Audit Log Improvements, and Security Hardening
- Self-Hosted Pro v1.8.0 — Color Skins, Rebuilt Forms, and More
Thank You
Thank you to everyone who contributed code, filed issues, and surfaced problems this cycle: @nullbenny for the sign-in throttle bypass report, @cgrard for the Prometheus metrics work, @OXERY for the remote font issue, @rennf93 for the CIDR proxy range fix, and @sadfun, @muskanbandta23, and @almokhtarbr for the new one-click deploy contributions.
Password Pusher will never have investor pressure to change its model, sell your data, or water-down & ruin what works. It's built on a simple idea: make it easy to share sensitive information securely, and keep it that way.
Thanks for reading this far — and for being part of this.
Peter Giacomo Lombardo & the Apnotic Team
- Hosted: pwpush.com
- Self-Hosted Pro: Self-Hosted Pricing
- Open Source: github.com/pglombardo/PasswordPusher
- Docker Images: pglombardo/pwpush
- Blog: docs.pwpush.com/blog