CVE-2023-49316: Phpseclib needs guardrails on large binaryfield integers

CVE-2023-49316 · Severity: low · CVSS 3.1 · Published 2026-05-08

Phpseclib needs guardrails on large binaryfield integers

Technologies: phpseclib/phpseclib (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2023-49316 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-49316 being exploited in the wild.
How severe is CVE-2023-49316?
Low severity, with a CVSS score of 3.1, published 8 May 2026.
Which products and versions are affected?
phpseclib/phpseclib (Packagist) ECOSYSTEM:introduced=3.0.0,fixed=3.0.34.
Is there a fix for CVE-2023-49316?
Yes. phpseclib/phpseclib (Packagist): upgrade to 3.0.34 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-49316?
Check whether you run phpseclib/phpseclib (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • phpseclib/phpseclib (Packagist): upgrade to 3.0.34 or later
    composer require phpseclib/phpseclib:^3.0.34

Affected products

  • phpseclib/phpseclib (Packagist) ECOSYSTEM:introduced=3.0.0,fixed=3.0.34

Identifiers

  • CVE-2023-49316
  • GHSA-2f25-pfq3-c7h8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.