Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD

CVE-2026-14355GHSA-7jrw-539f-x6vr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (php 8.5.8, 8.4.23, 8.3.32, 8.2.32; libphp 8.5.8, 8.4.23, 8.3.32, 8.2.32; php-min 8.5.8, 8.4.23, 8.3.32, 8.2.32), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Bitnami php

    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
    Fixed in
    8.5.8, 8.2.32, 8.4.23, 8.3.32

  • Bitnami libphp

    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
    Fixed in
    8.5.8, 8.2.32, 8.4.23, 8.3.32

  • Bitnami php-min

    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
    Fixed in
    8.5.8, 8.2.32, 8.4.23, 8.3.32

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2026-14355: 0.28% estimated exploitation activity in the next 30 days; percentile 20.53 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from osv record BIT-php-min-2026-14355

  2. Revision 2 · amended ·

    Amended from osv record BIT-php-2026-14355

  3. Revision 1 · created ·

    Published from osv record BIT-libphp-2026-14355

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-14355

Advisory: ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD
IDs: CVE-2026-14355, GHSA-7jrw-539f-x6vr
Record: https://patchnext.com/advisories/cve-2026-14355 (revision 3, source checked 11 Nov 2026, 07:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: php 8.5.8, 8.4.23, 8.3.32, 8.2.32; libphp 8.5.8, 8.4.23, 8.3.32, 8.2.32; php-min 8.5.8, 8.4.23, 8.3.32, 8.2.32. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami php: 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; fixed in 8.5.8, 8.2.32, 8.4.23, 8.3.32
- Bitnami libphp: 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; fixed in 8.5.8, 8.2.32, 8.4.23, 8.3.32
- Bitnami php-min: 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; fixed in 8.5.8, 8.2.32, 8.4.23, 8.3.32

## Suggested inspection (read-only)
- Bitnami php: check the installed version with your package manager.
- Bitnami libphp: check the installed version with your package manager.
- Bitnami php-min: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on php, libphp, php-min.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-libphp-2026-14355 (OSV record BIT-libphp-2026-14355 lists affected ranges: Bitnami libphp >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.8 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-2026-14355 (OSV record BIT-php-2026-14355 lists affected ranges: Bitnami php >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.8 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-min-2026-14355 (OSV record BIT-php-min-2026-14355 lists affected ranges: Bitnami php-min >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…