{"items":[{"id":"NVI-00007409","kind":"vulnerability","title":"phpseclib: X.509 certificate validation sends attacker-controlled outbound requests (server-side request forgery) via Authority Information Access","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m557-wrgg-6rp4","CVE-2026-55599"],"plain_summary":"GitHub lists this reviewed advisory for phpseclib/phpseclib, phpseclib/phpseclib, phpseclib/phpseclib. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-d31281066c6c5e477b36ebb48b2adaa8"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.0.30 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.0.55 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.54 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-08T17:37:11.000Z","value":"5.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-114492b1b595e7cdc7be78510cc20283"},{"kind":"CVSS","as_of":"2026-06-26T20:10:05.340Z","value":"5.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-37ca48c4f42de2404f144e4f9759f51e"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.213%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11605. Missing scores are unknown.","source_id":"sr-d31281066c6c5e477b36ebb48b2adaa8"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-114492b1b595e7cdc7be78510cc20283","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:51.634Z"},{"id":"sr-da93c30a35ddfe211951feb63b3eb99b","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.973Z"},{"id":"sr-37ca48c4f42de2404f144e4f9759f51e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55599","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55599","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:39.943Z"},{"id":"sr-d31281066c6c5e477b36ebb48b2adaa8","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55599","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.383Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 0.1.1, <= 1.0.29"]},{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 2.0.0, <= 2.0.54"]},{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 3.0.0, <= 3.0.53"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 0.1.1; fixed 1.0.30"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.55"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.54"]}],"null_published_at":"2026-11-08T01:52:04.807Z","source_updated_at":"2026-07-08T17:37:11.000Z","source_disclosed_at":"2026-06-16T15:03:58.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.973Z"},{"id":"NVI-00007409","kind":"vulnerability","title":"phpseclib: X.509 certificate validation sends attacker-controlled outbound requests (server-side request forgery) via Authority Information Access","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m557-wrgg-6rp4","CVE-2026-55599"],"plain_summary":"GitHub lists this reviewed advisory for phpseclib/phpseclib, phpseclib/phpseclib, phpseclib/phpseclib. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-37ca48c4f42de2404f144e4f9759f51e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.0.30 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.0.55 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.54 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-08T17:37:11.000Z","value":"5.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-114492b1b595e7cdc7be78510cc20283"},{"kind":"CVSS","as_of":"2026-06-26T20:10:05.340Z","value":"5.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-37ca48c4f42de2404f144e4f9759f51e"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-114492b1b595e7cdc7be78510cc20283","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:51.634Z"},{"id":"sr-da93c30a35ddfe211951feb63b3eb99b","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.973Z"},{"id":"sr-37ca48c4f42de2404f144e4f9759f51e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55599","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55599","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:39.943Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 0.1.1, <= 1.0.29"]},{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 2.0.0, <= 2.0.54"]},{"certainty":"source_listed","source_ids":["sr-114492b1b595e7cdc7be78510cc20283"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":[">= 3.0.0, <= 3.0.53"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 0.1.1; fixed 1.0.30"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.55"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.54"]}],"null_published_at":"2026-11-05T19:10:21.402Z","source_updated_at":"2026-07-08T17:37:11.000Z","source_disclosed_at":"2026-06-16T15:03:58.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.973Z"},{"id":"NVI-00007409","kind":"vulnerability","title":"phpseclib: X.509 certificate validation sends attacker-controlled outbound requests (server-side request forgery) via Authority Information Access","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m557-wrgg-6rp4","CVE-2026-55599"],"plain_summary":"OSV carries this publisher advisory for phpseclib/phpseclib, phpseclib/phpseclib, phpseclib/phpseclib. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.0.30 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.0.55 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.54 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-37ca48c4f42de2404f144e4f9759f51e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-26T20:10:05.340Z","value":"5.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-37ca48c4f42de2404f144e4f9759f51e"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-da93c30a35ddfe211951feb63b3eb99b","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.973Z"},{"id":"sr-37ca48c4f42de2404f144e4f9759f51e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55599","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55599","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:39.943Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 0.1.1; fixed 1.0.30"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.55"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.54"]}],"null_published_at":"2026-11-01T14:34:07.625Z","source_updated_at":"2026-09-10T03:51:08.986Z","source_disclosed_at":"2026-06-16T15:03:58.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.973Z"},{"id":"NVI-00007409","kind":"vulnerability","title":"phpseclib: X.509 certificate validation sends attacker-controlled outbound requests (server-side request forgery) via Authority Information Access","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m557-wrgg-6rp4","CVE-2026-55599"],"plain_summary":"OSV carries this publisher advisory for phpseclib/phpseclib, phpseclib/phpseclib, phpseclib/phpseclib. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.0.30 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.0.55 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.54 for phpseclib/phpseclib. Confirm the publisher’s latest guidance.","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-da93c30a35ddfe211951feb63b3eb99b","url":"https://github.com/advisories/GHSA-m557-wrgg-6rp4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m557-wrgg-6rp4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.973Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 0.1.1; fixed 1.0.30"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.55"]},{"certainty":"source_listed","source_ids":["sr-da93c30a35ddfe211951feb63b3eb99b"],"technology":"phpseclib/phpseclib","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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.\n\n### Details\n\nWhen no already-trusted certificate authority is the issuer of certificate under validation, **validateSignatureCountable()** continues to AIA fetching. Default for **validateSignature()** is **caonly = true**:\n\n```\n// phpseclib/File/X509.php:1316-1327 (4.0 development line, commit 74ada1a6)\nif (!isset($signingCert)) {\n    if ($caonly) {\n        return $this->testForIntermediate(true, $count) && $this->va","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.54"]}],"null_published_at":"2026-10-31T22:13:14.336Z","source_updated_at":"2026-09-10T03:51:08.986Z","source_disclosed_at":"2026-06-16T15:03:58.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.973Z"}],"next_cursor":null,"snapshot_revision":"40769"}