dbcve.org
PHPApplication

CVE-2026-14355

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-03
Fix available
A fix is available. Upgrade to 8.2.32 / 8.3.32 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In PHP versions 8.2.* before 8.2.32, 8.3.* before 8.3.32, 8.4.* before 8.4.23, 8.5.* before 8.5.8, the AES-WRAP-PAD algorithm implementation in OpenSSL extension contains a buffer allocation flaw. The output buffer for the AES key-wrap-with-padding operation is sized from the plaintext length without accounting for RFC 5649 expansion. This may cause OpenSSL to write beyond allocated memory, corrupting heap metadata and triggering application abort.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 6d ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In PHP versions 8.2.* before 8.2.32, 8.3.* before 8.3.32, 8.4.* before 8.4.23, and 8.5.* before 8.5.8, the AES-WRAP-PAD algorithm implementation in the OpenSSL extension contains a buffer allocation flaw where the output buffer is sized based on plaintext length without accounting for RFC 5649 expansion, causing out-of-bounds writes that corrupt heap metadata and trigger application abort.

MitigationUpgrade PHP to version 8.2.32, 8.3.32, 8.4.23, or 8.5.8 or later to resolve the buffer allocation flaw in the AES key-wrap-with-padding operation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PHPApplication
Affected:>= 8.2.0, < 8.2.32>= 8.3.0, < 8.3.32>= 8.4.0, < 8.4.23>= 8.5.0, < 8.5.8
Debian LinuxOperating system
Affected:= 12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PHP version
    Run `php -v` to display the PHP version number
    Affected if version is 8.2.x before 8.2.32, 8.3.x before 8.3.32, 8.4.x before 8.4.23, or 8.5.x before 8.5.8
  2. Confirm OpenSSL extension is loaded
    Run `php -m` or `php -i` and verify the openssl extension appears in the module list
    Affected if OpenSSL extension is present and PHP version falls within the affected ranges
  3. Check for AES key wrap with padding usage
    Search application source code for calls to openssl_encrypt or openssl_decrypt that specify AES-WRAP-PAD algorithm (look for 'aes-128-wrap-pad', 'aes-192-wrap-pad', 'aes-256-wrap-pad', or similar algorithm names in OpenSSL method parameter)
    Affected if application code uses the AES-WRAP-PAD algorithm with the vulnerable PHP/OpenSSL versions

Environment is affected if running a PHP version within the affected ranges AND the OpenSSL extension is loaded AND the application uses AES key wrap with padding functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.2.32 / 8.3.32 / 8.4.23 or later
Fixed in 8.2.328.3.328.4.23
Interim mitigation

Upgrade PHP to version 8.2.32, 8.3.32, 8.4.23, or 8.5.8 or later to resolve the buffer allocation flaw in the AES key-wrap-with-padding operation.

Recommended fix High confidence

PHP 8.5.8 (or 8.4.23+, 8.3.32+, 8.2.32+)

  1. 1. Identify the current PHP version by running: php -v
  2. 2. For Debian 12.0 systems, check available PHP packages: apt-cache policy php8.4-openssl (or php8.3-openssl, php8.2-openssl)
  3. 3. Upgrade PHP to a fixed version using your system's package manager: apt-get update && apt-get install php8.4 (or php8.3, php8.2)
  4. 4. Alternatively, upgrade to PHP 8.5.8 or later from source or official repos: https://www.php.net/downloads
  5. 5. Verify the upgrade was successful: php -v (should show 8.2.32+, 8.3.32+, 8.4.23+, or 8.5.8+)
  6. 6. Test that OpenSSL extension functions (openssl_encrypt, openssl_decrypt) work correctly with AES key-wrap operations
  7. 7. Restart any PHP-FPM or Apache/php-fpm services: systemctl restart php*-fpm or systemctl restart apache2
Caveat Major version upgrades (e.g., 8.2 to 8.3) may introduce breaking changes; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in PHP Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14355 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data