https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T23:41:13.862027+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-01263 bdu:2025-01263 2026-10-16T23:41:13.879516+00:00 bdu:2025-01263 https://cve.radiocsirt.org/vuln/euvd-2026-202903 EUVD-2026-202903 2026-10-16T23:41:13.879553+00:00 EUVD-2026-202903 https://cve.radiocsirt.org/vuln/fkie_cve-2024-52796 fkie_cve-2024-52796 2026-10-16T23:41:13.879567+00:00

Password Pusher, an open source application to communicate sensitive information over the web, comes with a configurable rate limiter. In versions prior to v1.49.0, the rate limiter could be bypassed by forging proxy headers allowing bad actors to send unlimited traffic to the site potentially causing a denial of service. In v1.49.0, a fix was implemented to only authorize proxies on local IPs which resolves this issue. As a workaround, one may add rules to one's proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.

 https://cve.radiocsirt.org/vuln/ghsa-ffp2-8p2h-4m5j GHSA-ffp2-8p2h-4m5j — Password Pusher rate limiter can be bypassed by forging proxy headers 2026-10-16T23:41:13.879601+00:00

Affected: RubyGems: pwpush

### Impact

Password Pusher comes with a configurable rate limiter. In versions prior to [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), the rate limiter could be bypassed by forging proxy headers allowing bad actors to send unlimited traffic to the site potentially causing a denial of service.

Additionally, with the ability to bypass rate limiting, it also allows attackers to more easily execute brute force attacks.

### Patches

In [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), a fix was implemented to only authorize proxies on local IPs which resolves this issue.

If you are running a remote proxy, please see [this documentation](https://docs.pwpush.com/docs/proxies/#trusted-proxies) on how to authorize the IP address of your remote proxy.

### Workarounds

It is highly suggested to upgrade to at least [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0) to mitigate this risk.

If for some reason you cannot immediately upgrade, the alternative is that you can add rules to your proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.

### References

The new settings are [configurable to authorize remote proxies](https://docs.pwpush.com/docs/proxies/#trusted-proxies).

### Credits

Thank you to [Positive Technologies](https://www.ptsecurity.com/ww-en/) for reporting and working with me to bring this CVE to the community with the associated fix.