https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T09:34:02.667328+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cleanstart-2026-ck66622 CLEANSTART-2026-CK66622 — Security fix for CVE-2026-47737 applied in: logstash-fips 9.4.3-r1 2026-10-03T09:34:02.670743+00:00

Affected: CleanStart: logstash-fips

Security vulnerability affects the logstash-fips package. This issue is resolved in later releases. See references for vulnerability details.

 https://cve.radiocsirt.org/vuln/euvd-2026-337961 EUVD-2026-337961 2026-10-03T09:34:02.670791+00:00 EUVD-2026-337961 https://cve.radiocsirt.org/vuln/fkie_cve-2026-47737 fkie_cve-2026-47737 2026-10-03T09:34:02.670807+00:00

Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.

 https://cve.radiocsirt.org/vuln/ghsa-2vqw-3mp8-cgmx GHSA-2vqw-3mp8-cgmx — Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections 2026-10-03T09:34:02.670830+00:00

Affected: RubyGems: puma

### Impact

Puma is vulnerable to source IP spoofing when `set_remote_address proxy_protocol: :v1` is enabled and persistent connections are used.

PROXY protocol v1 is a connection-level protocol. [Support was added to Puma in v5.5.0](https://github.com/puma/puma/issues/2651). A proxy sends one PROXY header at the beginning of a TCP connection, before any HTTP data. Puma incorrectly re-parsed PROXY protocol headers after each keep-alive request on the same connection. An attacker able to send HTTP requests through a trusted proxy could therefore inject a second PROXY header between HTTP requests. Puma would treat the injected header as authoritative for the next request and overwrite `REMOTE_ADDR`.

This can mislead applications or middleware that use `REMOTE_ADDR` for security decisions, rate limiting, auditing, or allow/deny lists.

**Only deployments that explicitly enable PROXY protocol v1 are affected**, and will have set:

```ruby set_remote_address proxy_protocol: :v1 ```

Puma's default configuration is not affected. Deployments that do not use persistent connections to Puma are also not expected to be affected by this issue.

### Patches

Users should upgrade to versions 7.2.1 or 8.0.2.

### Workarounds

Disable PROXY protocol v1 parsing if it is not required:

```ruby # remove/comment this: # set_remote_address proxy_protocol: :v1 ```

Users can also disable persistent connections to Puma, for example:

```ruby enable_keep_alives false ```

### References…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-47737 UBUNTU-CVE-2026-47737 2026-10-03T09:34:02.670876+00:00

Affected: Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: puma, Ubuntu:24.04:LTS: puma, Ubuntu:26.04:LTS: puma

Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.