Why Should I Care? β€” 2026-10-22 | πŸ”΄ 3 HIGH Β· 🟑 0 MEDIUM Β· πŸ”΅ 12 RADAR Β· βšͺ 182 FILTERED

πŸ“‹ Briefing β€” 2026-10-22

15 vendor intel items scanned  |  πŸ”΄ 3 HIGH  |  🟑 0 MEDIUM  |  πŸ”΅ 12 RADAR  |  βšͺ 182 FILTERED

πŸ”΄ Critical β€” action required:

  1. Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619) β€” CVSS 9.2 β€” critical severity, immediate attention required.
  2. Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot (CVE-2026-109618, CVE-2026-109619) β€” Yes, if you run any unpatched PHP version: PHP2Shell is being actively exploited in the wild, with attacks observed four days before public disclosure, meaning compromise may have already occurred.
  3. PHP core RCE vulnerability patches (CVE-2026-109618 and CVE-2026-109619) (CVE-2026-109618) β€” Yes, if you run FortiADC, FortiClient EMS, FortiDDoS, FortiSIEM, FortiMonitor, FortiClient Cloud, or FortiSOAR: these products are under investigation for a critical unauthenticated RCE vulnerability in the PHP core.

Everything else can wait.

πŸ”΅ 12 items on the radar β€” see below ↓


πŸ”΄ HIGH β€” Handle Now


Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619)

AWS Security Blog

CVSS 9.2 β€” critical severity, immediate attention required.

🎯 Affected: AWS


Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot

AWS Security Blog | CVE-2026-109618, CVE-2026-109619

❓ Why Should I Care?
Yes, if you run any unpatched PHP version: PHP2Shell is being actively exploited in the wild, with attacks observed four days before public disclosure, meaning compromise may have already occurred.

🎯 Affected versions: All PHP versions prior to the fixed releases (specific version ranges not explicitly listed in advisory, but implies all versions lacking the patch for CVE-2026-109618/19)
Not affected: PHP versions containing the fix for CVE-2026-109618 and CVE-2026-109619

🎭 In plain English:
This is a critical vulnerability in PHP that allows attackers to execute arbitrary code on your server. An attacker could send a specially crafted file upload request to your website, which would then run malicious commands, potentially giving them full control over your server, allowing them to steal data, install malware, or disrupt services.

πŸ”§ Prerequisites:

  • Running an unpatched version of PHP
  • Internet-facing PHP application
  • Multi-part file uploads enabled

⏱ Urgency: Immediate patching is required as exploitation is active in the wild and may have started before the public disclosure date.

βœ… Fixed in: PHP versions fixed for CVE-2026-109618 and CVE-2026-109619 (exact version numbers not specified in advisory, refer to PHP release notes)

πŸ’‘ Context: The root cause is a vulnerability in PHP's handling of file uploads that allows for remote code execution.


PHP core RCE vulnerability patches (CVE-2026-109618 and CVE-2026-109619)

Fortinet PSIRT | CVSS 9.8 | CVE-2026-109618

❓ Why Should I Care?
Yes, if you run FortiADC, FortiClient EMS, FortiDDoS, FortiSIEM, FortiMonitor, FortiClient Cloud, or FortiSOAR: these products are under investigation for a critical unauthenticated RCE vulnerability in the PHP core.

🎯 Affected versions: FortiADC, FortiADC Manager, FortiClient EMS, FortiDDoS, FortiDDoS-F, FortiSIEM, FortiMonitor, FortiClient Cloud, FortiSOAR, FortiSOAR PaaS (versions under investigation)
Not affected: FortiOS, FortiManager, FortiAnalyzer, FortiWeb, FortiMail, FortiClient Linux, FortiClient Windows, FortiClient MacOS, FortiSASE, FortiAuthenticator, FortiSwitch, FortiNAC

🎭 In plain English:
The PHP engine used by these Fortinet products has a flaw where it fails to properly clean up memory when it runs out of space. An attacker can exploit this to execute arbitrary code on the server without needing a login. For example, an attacker could send a specific request that causes the server to crash in a way that leaves 'junk' data in memory, then trick the server into running that junk as code, giving the attacker full control of the system.

πŸ”§ Prerequisites:

  • Running a Fortinet product listed as 'Under Investigation' (e.g., FortiADC, FortiSIEM, FortiSOAR)
  • The product must be running a version of PHP that is vulnerable to the OOM longjmp issue
  • Network access to the affected service

⏱ Urgency: Critical urgency because this is an unauthenticated remote code execution vulnerability with a CVSS of 9.8, and Fortinet is actively investigating which specific versions are impacted.

πŸ’‘ Context: The root cause is PHP's use of longjmp() for out-of-memory errors, which can leave request memory in an uninitialized state that is later read or branched on during cleanup.


🟑 MEDIUM (0)

None.


πŸ”΅ On the Radar (12)


βšͺ 182 low-priority items filtered.


πŸ¦… Aggregated and triaged by Donna AI  |  Sources: 8 vendor feeds  |  CISA KEV

Subscribe to Why Should I Care?

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe