China Netel logoChina Netel
NEWS

Impact of the PHP2Shell vulnerability on Avaya products, and what to do about it

Impact of the PHP2Shell vulnerability on Avaya products, and what to do about it
PHP2Shell vulnerability and its impact across Avaya product lines (vendor image)

1. Why this vulnerability is dangerous

The problem lies in PHP's internal memory management. CVE-2026-109618 is improper handling of memory exhaustion: PHP aborts the request when out of memory, but the cleanup routine treats incompletely initialized data as valid, corrupting memory. CVE-2026-109619 is a classic use-after-free: some global state is not properly reset when a request ends, so the next request handled by the same worker reads stale data.

What both have in common is that an attacker needs no account and no application-level flaw: anyone able to send a crafted HTTP request to the web service (typically oversized headers or a deeply nested multipart form) has a chance of gaining system privileges. The risk is highest in Apache mod_php deployments; published proofs of concept show that an unauthenticated request can reach the attack path before any application code executes.

The official fixed versions are PHP 8.2.35 / 8.3.36 / 8.4.27 / 8.5.12. The end-of-life PHP 5, 7, 8.0 and 8.1 branches no longer receive official patches.

As for why communications systems are affected, Avaya says it plainly in the PSN: the PHP code embedded in its products contains these vulnerabilities. Management interfaces, administration portals and reporting modules in communications platforms rely heavily on PHP, so the flaw at the foundation propagates to the whole appliance.

2. Affected products and patch matrix

The u suffix on a PSN number means the advisory is continuously updated, and fixes for some older versions are still in progress, so subscribing to Avaya E-notifications is recommended.

Product / PSNAffected versionsOfficial remediation
Communication Manager PSN006512uAll versions10.1 -> patch cm-10.1-php2shell-vuln-fix.tar. 10.2 -> SSP23 (released 10-26). 10.3 -> SSP01 (released 10-28). 8.1.x -> private patch (released 10-29; a valid maintenance contract is required, obtain it by raising a Service Request with Avaya).
Application Enablement Services PSN006513uAll versions10.1 -> patch aes-10.1-php2shell-vuln-fix.tar.gz. 10.2 -> SSP23 (released 10-26). 10.3 -> SSP01 (released 10-28).
Aura Device Services PSN006516uAll versions10.1.x -> patch aads-10.1-php2shell-vuln-fix.bin. 10.2.0.x -> upgrade to 10.2.1 first, then apply SSP24. 10.2.1.x -> SSP24 (released 10-26). 10.3 -> SSP01 (released 10-28). 8.1.x -> patch (released 10-29).
IP Office PSN006518uAll versions12.x -> CP, download PHP2SHELL_CVE-2026-109618-109619_12.x.zip with IP Office 12.3 GA. 11.1.x -> CP, download with 11.1 FP3 SP2 GA. 11.0.x / 10.x -> CP, download with 11.0 FP4 SP8 GA.
Avaya Meetings Server PSN006517uAll versions9.1.15.x / 9.1.14.x -> apply Hotfix SSP-045-25.zip, run through the iView Web UI on Meetings Management and Media Server. 9.1.13.x -> migrate to 9.1.14.x or 9.1.15.x first.
Avaya Analytics PSN006510u4.1.x / 4.2.x / 4.3.x (including all patch levels)4.0.x / 4.1.x -> upgrade to 4.2 or later, then apply the matching patch. 4.2.x -> Patch 002_1 / 006 (11-06 / 11-11). 4.3.0.x -> Patch 002_2 / 008 (11-06). 4.3.1.x -> Patch 002 (11-11), Patch 003 (released). 4.3.1.2 -> the release already contains the fix.
Aura Web Gateway PSN006514uAll versions10.1.x -> upgrade to Aura 10.2 first, then apply AAWG 10.2 SSP13. 10.2.x -> SSP13 (released 10-28; see PSN006522u for installation). 10.3 -> not affected.
Avaya Experience Portal PSN006515u8.x8.1.2.x -> upgrade to AVL Patch 2607 / 2609, then apply PHP_Hotfix_2610.tar.gz. 8.1.1 / 8.1.0 -> the same path of AVL patch plus PHP hotfix. Applies only to Avaya RHEL (AVL) deployments; software-only deployments are not covered.

Two details are worth noting. First, the PHP package in AAWG is not actually used, so Avaya's approach is to remove it outright: log in to the CLI as admin, switch to root and run rpm -ev `rpm -qa | grep php`, without waiting for an SSP window. Second, after patching IP Office, version-based vulnerability scanners may still report the flaw: for 11.1.x and earlier Avaya back-ported the fixes and rebuilt the RPM without changing the version number, which is expected behaviour, so do not patch again on that basis.

3. Some earlier versions, where fixes are still in progress

For CM 6.x and earlier, 7.x, AES 6.x / 7.x / 8.x, AADS 7.1.x, Analytics 3.x, AAWG 3.x and Meetings 9.1.12.0 and earlier, Avaya has not yet published a fix; the PSNs will be updated as work progresses.

Some of these systems are already at or near end of support, so waiting for a patch may not be the best option. A more practical approach is to remove management interfaces from the internet and office network segments, allowing access only from operations terminals through a jump host, while limiting multipart request size and nesting depth at the perimeter and planning version upgrades in parallel.

4. Interim mitigations for the patching window

Until upgrades are complete, the interim measures recommended by the PHP project and national CERTs can significantly reduce the chance of exploitation, but they are mitigation only and no substitute for patching:

  • Disable the upload progress feature: session.upload_progress.enabled=Off, then reload PHP-FPM. This alone cuts off the verified attack path and delivers the biggest benefit;
  • On PHP 8.5 environments, set fatal_error_backtraces=0 and restart the workers;
  • Lock memory_limit through the FPM pool's php_admin_value so attackers have no room to push a worker into OOM;
  • Tighten request bodies: lower post_max_size to 8M (32M where uploading is a business need), limit header count, multipart part count and nesting depth at the gateway, and set WAF emergency rules to block rather than log only.

One counter-intuitive warning: do not use RLIMIT_AS or RLIMIT_DATA to limit PHP process memory. Hitting either limit makes mmap() fail, which pushes the request straight into the CVE-2026-109618 exploit path.

5. How we can help

As an Avaya Diamond Partner we have reviewed all eight PSNs one by one. Send us your list of system versions and we will tell you directly which patch applies to each device, whether it has been released and whether an upgrade is needed first, and flag the nodes with no patch available that can only be protected by isolation.

On patch access, restricted patches such as those for CM and AADS 8.1.x require a valid maintenance contract; we can verify contract status and raise the Service Request on your behalf, and we support implementation remotely or on site. If you suspect a system has already been exploited, we can also help with log forensics and investigation of anomalous processes.

6. Need help investigating?

If you run any of the products above and want to confirm the affected scope and remediation path, please get in touch; we can start with an impact assessment by version.

Want product announcements first?

Leave your contact details and we will proactively share major security advisories and product changes.

Contact Us
Call Us