CVE-2026-62382

PasswordPusher before v2.9.6 Authentication Bypass via Null Comparison

Published Aug 22, 2026 CVSS 4.0 · 6.9 Medium EPSS 1.2% KEV · Not listed
Description
PasswordPusher versions v1.45.11 through v2.9.5 contain an improper authorization vulnerability in the push deletion logic. The ownership check compares @push.user against current_user; for an anonymously created push both values are nil, and Ruby evaluates nil == nil as true, so the check passes and the deletable_by_viewer restriction is never enforced. An attacker who knows only the secret URL can permanently delete an anonymous push even when the creator disabled viewer deletion and even without the passphrase. Only deployments that allow anonymous pushes (the default) are affected. The issue is fixed in v2.9.6.

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker who knows a secret URL to permanently delete an anonymous push. The push deletion logic compares the push owner against the current user; when both are nil, Ruby treats nil == nil as true, so the deletion restriction is bypassed. Consequently, an attacker can erase data even when the push creator disabled viewer deletion and without the passphrase, causing loss of information.

Affected Systems

The affected product is PasswordPusher version 1.45.11 through 2.9.5. Any instance that allows anonymous pushes—which is the default—is vulnerable. The issue is fixed in 2.9.6.

Risk and Exploitability

With a CVSS score of 6.9 the vulnerability is of moderate severity. EPSS data is not available and it is not listed in the CISA KEV catalog, but the problem can be exploited remotely by anyone who possesses the secret URL. No authentication is required, making the attack path straightforward and likely to be used if discovered.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade PasswordPusher to version 2.9.6 or later, which corrects the ownership check in push deletion logic.
  • If an immediate upgrade is not possible, disable anonymous push creation in the application settings to prevent the bypass from being usable.
  • As an additional temporary measure, enforce viewer deletion or require a passphrase for deletion of anonymous pushes by adjusting the deletion controls or applying a code patch until the official update is applied.

Generated by OpenCVE AI on August 22, 2026 at 13:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Pglombardo
Pglombardo password Pusher
Vendors & Products Pglombardo
Pglombardo password Pusher
Type Values Removed Values Added
Description PasswordPusher versions v1.45.11 through v2.9.5 contain an improper authorization vulnerability in the push deletion logic. The ownership check compares @push.user against current_user; for an anonymously created push both values are nil, and Ruby evaluates nil == nil as true, so the check passes and the deletable_by_viewer restriction is never enforced. An attacker who knows only the secret URL can permanently delete an anonymous push even when the creator disabled viewer deletion and even without the passphrase. Only deployments that allow anonymous pushes (the default) are affected. The issue is fixed in v2.9.6.
Title PasswordPusher before v2.9.6 Authentication Bypass via Null Comparison
Weaknesses CWE-863
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 31, 2026, 4:54 PM
Reserved
Jul 13, 2026, 10:40 PM
Status
Deferred
Published
Aug 22, 2026, 1:16 PM
Modified
Oct 12, 2026, 4:10 PM