https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T05:02:32.347403+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-15489 bdu:2026-15489 2026-10-03T05:02:32.452978+00:00 bdu:2026-15489 https://cve.radiocsirt.org/vuln/euvd-2026-329328 EUVD-2026-329328 2026-10-03T05:02:32.453023+00:00 EUVD-2026-329328 https://cve.radiocsirt.org/vuln/fkie_cve-2026-55599 fkie_cve-2026-55599 2026-10-03T05:02:32.453038+00:00

phpseclib is a PHP secure communications library. From 0.1.1 until 1.0.30, 2.0.55, and 3.0.54, when an application validates an untrusted X.509 certificate with phpseclib, X509::validateSignature() reads a URL out of that certificate's Authority Information Access (AIA) extension and connects to it. Attacker who supplies certificate fully controls host, port, and path of that connection. URL fetching is enabled by default, and no destination is blocked. An unauthenticated attacker can therefore make a validating server open connections to internal hosts and ports it should never reach, for example loopback 127.0.0.1, cloud metadata address 169.254.169.254, and internal-only services. This is a server-side request forgery (SSRF) caused by an insecure default. This vulnerability is fixed in 1.0.30, 2.0.55, and 3.0.54.

 https://cve.radiocsirt.org/vuln/ghsa-m557-wrgg-6rp4 GHSA-m557-wrgg-6rp4 — phpseclib: X.509 certificate validation sends attacker-controlled outbound requests (server-side request forgery) via A… 2026-10-03T05:02:32.453076+00:00

Affected: Packagist: phpseclib/phpseclib

### Summary

When an application validates an untrusted X.509 certificate with phpseclib, **X509::validateSignature()** reads a URL out of that certificate's Authority Information Access (AIA) extension and connects to it. Attacker who supplies certificate fully controls host, port, and path of that connection. URL fetching is enabled by default, and no destination is blocked. An unauthenticated attacker can therefore make a validating server open connections to internal hosts and ports it should never reach, for example loopback **127.0.0.1**, cloud metadata address **169.254.169.254**, and internal-only services. This is a server-side request forgery (SSRF) caused by an insecure default. It is reproducible on current released LTS 3.0.53 and on 4.0 development line.

### Details

When no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:

``` // phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6) if (!isset($signingCert)) { if ($caonly) { return $this->testForIntermediate(true, $count) && $this->validateSignature(true); } else { try { $this->testForSelfSigned(); $signingCert = $this; } catch (BadMethodCallException) { return $this->testForIntermediate(true, $count) && $this->validateSignature(true); } } } ```

**testForInter…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-55599 UBUNTU-CVE-2026-55599 2026-10-03T05:02:32.453151+00:00

Affected: Ubuntu:Pro:16.04:LTS: phpseclib, Ubuntu:Pro:18.04:LTS: phpseclib, Ubuntu:Pro:20.04:LTS: phpseclib, Ubuntu:Pro:22.04:LTS: phpseclib, Ubuntu:Pro:24.04:LTS: phpseclib, Ubuntu:25.10: phpseclib, Ubuntu:Pro:26.04:LTS: phpseclib

phpseclib is a PHP secure communications library. From 0.1.1 until 1.0.30, 2.0.55, and 3.0.54, when an application validates an untrusted X.509 certificate with phpseclib, X509::validateSignature() reads a URL out of that certificate's Authority Information Access (AIA) extension and connects to it. Attacker who supplies certificate fully controls host, port, and path of that connection. URL fetching is enabled by default, and no destination is blocked. An unauthenticated attacker can therefore make a validating server open connections to internal hosts and ports it should never reach, for example loopback 127.0.0.1, cloud metadata address 169.254.169.254, and internal-only services. This is a server-side request forgery (SSRF) caused by an insecure default. This vulnerability is fixed in 1.0.30, 2.0.55, and 3.0.54.