Out-of-bounds write in bccomp() via crafted operand and scale

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-17544: 0.42% estimated exploitation activity in the next 30 days; percentile 36.41 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Attacker-provided inputs to bccomp() could lead to an out-of-bounds write with stack and heap corruption in PHP versions from 8.4.* before 8.4.24 and from 8.5.* before 8.5.9.

Published by the source

17 Aug 2026, 05:47 UTC

Last modified by the source

11 Nov 2026, 02:55 UTC

Source last checked

11 Nov 2026, 07:45 UTC

1. Revision 3 · amended · 11 Nov 2026

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

2. Revision 2 · amended · 11 Nov 2026

   Amended from osv record BIT-php-2026-17544

3. Revision 1 · created · 11 Nov 2026

   Published from osv record BIT-libphp-2026-17544

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

# Patch Next advisory brief: CVE-2026-17544

Advisory: Out-of-bounds write in bccomp() via crafted operand and scale
IDs: CVE-2026-17544, GHSA-x692-q9x7-8c3f
Record: https://patchnext.com/advisories/cve-2026-17544 (revision 3, source checked 11 Nov 2026, 07:45 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.9, 8.4.24; libphp 8.5.9, 8.4.24; php-min 8.5.9, 8.4.24. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami php: affected >= 8.4.0, < 8.4.24; >= 8.5.0, < 8.5.9; fixed in 8.5.9, 8.4.24
- Bitnami libphp: affected >= 8.4.0, < 8.4.24; >= 8.5.0, < 8.5.9; fixed in 8.5.9, 8.4.24
- Bitnami php-min: affected >= 8.4.0, < 8.4.24; >= 8.5.0, < 8.5.9; fixed in 8.5.9, 8.4.24

## 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-17544 (OSV record BIT-libphp-2026-17544 lists affected ranges: Bitnami libphp >=8.4.0 =8.5.0 <8.5.9 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-2026-17544 (OSV record BIT-php-2026-17544 lists affected ranges: Bitnami php >=8.4.0 =8.5.0 <8.5.9 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-min-2026-17544 (OSV record BIT-php-min-2026-17544 lists affected ranges: Bitnami php-min >=8.4.0 =8.5.0 <8.5.9 (fixed))

Commands are suggestions: review each one before running it.