### Summary
A PPM or PGM file can declare a width of 0, which Pillow accepts, producing an image of size `(0, N)`. Passing that image to `ImageMorph.MorphOp.apply()` makes the native morphology code index a row buffer at `outrow[width - 1]`, which is `outrow[-1]` when the width is 0. The process crashes.
### Details
The PPM parser reads width and height with no lower-bound check:
- `src/PIL/PpmImagePlugin.py:119`
The native `apply()` writes the row edges with no guard that the width is positive:
- `src/_imagingmorph.c:81` sets `outrow[0] = outrow[width - 1] = 0;`
`match()` and `get_on_pixels()` use the same edge-indexing pattern.
### PoC
```python
from PIL import Image, ImageMorph
# A width-0 image (also producible from a crafted PPM header). apply() indexes
# outrow[width - 1] == outrow[-1] in native code.
im = Image.new("L", (0, 5))
ImageMorph.MorphOp(op_name="dilation4").apply(im)
```
Run it:
```
$ python 03_poc.py
Segmentation fault (core dumped)
```
Observed on a source build of commit `3e2ab96`.
Under AddressSanitizer:
```
==ERROR: AddressSanitizer: SEGV on unknown address (pc ... in apply)
#0 apply src/_imagingmorph.c:81
SUMMARY: AddressSanitizer: SEGV src/_imagingmorph.c:81 in apply
```
With width 0 the `outrow[width - 1]` write lands on an unmapped page, so it surfaces as a SEGV pinned to the edge-write line rather than a redzone overflow.
### Impact
Out-of-bounds write in a C extension. Affects any application that runs a morphology operation on an image opened from untrusted input. Result is a crash and possible memory corruption.
Exposed dangerous method or function and Incorrect Authorization vulnerability in OnePlus OxygenOS on Android. The olc2 logging HAL exposes a binder method that fork()'s and calls execl("/vendor/bin/sh", "sh", "-c", cmd, NULL) with a caller-supplied command string. The only authorization check is getCallingUid() == 0. Because SELinux policy grants binder access to this HAL to a wide client attribute, any uid-0 process in any of those domains (including dumpstate, which is reachable from an unprivileged app via Vulnerability 1) obtains arbitrary command execution. The spawned shell lands in u:r:vendor_qti_init_shell:s0 SELinux context via a policy type_transition, a domain holding all Linux capabilities. This issue affects OxygenOS: from 16.1.0 before 16.1.10.500, from 16.0.0 before 16.0.5.1200, and from 15.0.0 before 15.0.0.2000.
CVE-2026-70386 is a high-severity OS command injection vulnerability in OnePlus OxygenOS affecting versions from 15.0.0 before 15.0.0.2000 and from 16.0.0 before 16.0.5.1200. It allows any locally installed Android app, without declared permissions or user interaction beyond launch, to execute arbitrary shell commands as root in a specific SELinux domain. The flaw arises from an unauthorized binder interface accepting event data that is unsafely passed to a system command, leading to privilege escalation.
The Jane Menu WordPress plugin before 1.5.1 does not have any capability or nonce checks on one of its form handlers, which is reachable by unauthenticated users, allowing them to bind any published page to a remote document of their choosing. The plugin then fetches that document and outputs its head and body into the page without escaping, so an unauthenticated attacker can run arbitrary JavaScript in the browser of any visitor to that page, including an administrator.
This security update for Mozilla Firefox Extended Support Release 153.5.0 ESR addresses multiple vulnerabilities across various components including privilege escalation, sandbox escapes, use-after-free bugs, incorrect boundary conditions, information disclosure, mitigation bypasses, race conditions, integer overflows, spoofing, and denial-of-service issues. Additionally, a use-after-free vulnerability in libexpat is fixed. These issues collectively affect core browser functionality such as networking, graphics, JavaScript engine, DOM, storage, and security sandboxing.
Two critical PHP remote code execution vulnerabilities will be patched in an emergency release on October 21. Fixes are only expected for supported PHP 8.x branches. Key takeaways CVE-2026-109618 and CVE-2026-109619 are critical vulnerabilities in PHP, both rated CVSSv4.0 9.2 by the PHP security team. Public reporting describes both as remote code execution vulnerabilities. watchTowr says it believes it has reproduced CVE-2026-109618, and Cloudflare CTO Dane Knecht says the company is seeing early attacks emerging. The patch release is scheduled for October 21, 2026 at 14:00 UTC. Version numbers reported before the release point to PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. End-of-life branches are not expected to receive fixes. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding two critical vulnerabilities in PHP that were announced on October 20, 2026. FAQ When were these PHP vulnerabilities first disclosed? On October 20, 2026, the CVE identifiers circulated on Hacker News and social media. Later that day, the PHP security team published an advance notice of a security release scheduled for October 21 at 14:00 UTC (10:00 AM ET) to address two critical vulnerabilities. The notice said the team could release earlier if details became public or if exploitation appeared in the wild. CERT-EU also published an advisory (2026-018) naming both CVEs. According to watchTowr , the vulnerabilities were originally set to be disclosed on Thursday, October 22, under embargo. A video shared by researcher Kirill Firsov demonstrates the exploit chain, dubbed php2shell. Firsov credited the video and exploit to researcher LCFR and Calif.io. The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence. — The PHP Foundation (@ThePHPF) October 20, 2026 What are CVE-2026-109618 and CVE-2026-109619? CVE Description CVSSv4.0 CVE-2026-109618 Unspecified PHP Vulnerability 9.2 CVE-2026-109619 Unspecified PHP Vulnerability 9.2 CVE-2026-109618 and CVE-2026-109619 are critical vulnerabilities in PHP. Public reporting describes both as remote code execution vulnerabilities. The PHP security team has not published technical details before the patch release. CVSS scores differ across sources. The PHP security team rates both vulnerabilities as CVSSv4.0 9.2. Some early reports, including watchTowr and a Hacker News post, describe them as CVSS 10.0. We will update this blog once PHP publishes its advisory. Which PHP versions are affected? CERT-EU says these vulnerabilities could affect all PHP versions from PHP 5 onwards, and the demonstration video references PHP 5.4.0 and later. PHP will publish the official list of affected and fixed versions with the release. Before the release, security researcher Kevin Beaumont reported the following fixed versions: Affected Versions Fixed Version (expected) PHP 8.5.x 8.5.12 PHP 8.4.x 8.4.27 PHP 8.3.x 8.3.36 PHP 8.2.x 8.2.35 PHP 5.x through 8.1.x End-of-life, no fix expected Linux distributions that ship older PHP packages may backport fixes, so organizations using distribution packages should check their vendor's advisories. How widespread is PHP, and how many hosts are potentially affected? According to W3Techs , PHP is used by 69.3% of websites whose server-side language is known. Platforms such as WordPress, Drupal, Joomla, Laravel and Magento all run on PHP. Security researcher Silas Cutler's rough estimate is that over 1.3 million internet-exposed hosts are potentially vulnerable. A Shodan search by Henk Poley counts over 1.9 million internet-exposed hosts running PHP. Has exploitation been observed in the wild? On October 21, Cloudflare CTO Dane Knecht said the company is "seeing early attacks emerging" and is updating its miti…
The Download Manager WordPress plugin before 3.3.71, Download Manager WordPress plugin before 7.5.9 does not have CSRF checks in some places, allowing attackers to make a logged in admin update its privacy and storage settings via a crafted link, including the credential that gates its unauthenticated maintenance endpoint.
The Elementor Website Builder WordPress plugin before 4.3.5 does not sanitize the text content of SVG files, checking only their elements and attributes, allowing users with the Contributor role and above to store a payload which breaks out when the SVG is rendered inline in a page and executes in the browser of any user viewing it. Execution is specific to Chromium-based browsers; Firefox is not affected.
The Elementor Website Builder WordPress plugin before 4.3.5 does not sanitize uploaded SVG files on every upload route, allowing users with the Author role and above to upload a file containing JavaScript, which will run in the browser of any user who opens it. Exploitation requires unfiltered file uploads to be enabled in the Elementor Website Builder WordPress plugin before 4.3.5 settings, which is not the default.
The SureCart WordPress plugin before 4.9.5 does not restrict which related objects an anonymous visitor may include when reading a single upsell funnel through its REST API, nor strip private fields from those objects, allowing unauthenticated users to read merchant-private catalog data such as pricing, commission, stock, SKU and tax internals, including unpublished products.
The Duplicator and Duplicator Pro WordPress plugins are vulnerable to PHP Object Injection via deserialization of untrusted data in versions up to 1.5.17 and 4.6.10 respectively. This flaw allows unauthenticated attackers to inject serialized objects into public site content, which are later processed during migration or import operations by an administrator. Exploitation can lead to remote code execution or deletion of critical files such as wp-config.php, potentially resulting in site takeover. The vulnerability requires a sequence of actions: an attacker stores malicious serialized data, an administrator creates a package, and then performs a migration or import that triggers the deserialization. No official patch information is provided in the data.
Dulwich versions from 0.22.5 up to but not including 1.2.8 contain a path traversal vulnerability. This flaw allows an attacker with local access and user interaction to potentially read, modify, or delete files outside the intended directory. The vulnerability has a high severity rating with a CVSS score of 7.8. Multiple specific package versions, including various Ubuntu builds, are affected.
Astral uv versions before 0.8.22 contain a path traversal vulnerability that allows unauthorized modification of data. This vulnerability has a CVSS score of 6.5, indicating a medium severity level. The affected versions include specific builds of version 0.9.17+ds1. There is no indication of public exploits or active exploitation in the wild. No patch or remediation details are provided in the available data.
Vyper versions 0.3.8 through 0.5.0b1 contain an optimizer miscompilation bug that causes certain ternary expressions involving bitwise OR operations with nonzero integer literals to be incorrectly compiled to the constant 1. This flaw leads to incorrect values being used in storage writes, arithmetic operations, indexes, return values, or events, potentially causing deposits to be recorded incorrectly and funds to be locked without warning or revert.
Trigger.dev versions before 4.5.6 deployed via self-hosted Docker Compose with default secrets allow authentication bypass due to a hardcoded MAGIC_LINK_SECRET. This enables unauthenticated attackers to forge valid magic link tokens, log in as any email address, and access backend services like Postgres, Redis, and ClickHouse using default credentials, compromising all tenant data.
Trigger.dev versions prior to 4.5.6 have an authorization bypass vulnerability in the DeleteTaskScheduleService and SetActiveOnTaskScheduleService components. This flaw allows authenticated users to delete or disable schedules belonging to other organizations by exploiting user-controlled keys. Attackers can misuse their own project's schedule route with a victim's schedule friendlyId to manipulate and destroy other organizations' imperative cron schedules.
Trigger.dev versions prior to 4.5.10 contain a server-side request forgery (SSRF) vulnerability that allows authenticated project members to bypass webhook SSRF protections by targeting the 198.18.0.0/15 benchmarking IP range. This enables attackers to perform blind internal probing and limited state-changing POST requests to internally routed services within this range.
An information leak vulnerability exists in ANGLE component of Google Chrome on Windows versions prior to 156.0.8078.47. This flaw allows a remote attacker to leak sensitive information by convincing a user to visit a crafted HTML page. The vulnerability has a medium severity rating with a CVSS score of 6.5.
CVE-2026-113737 is a path traversal vulnerability in the R6410418 Jackrong-llm-finetuning-guide project affecting the validate_indexed_tensors function in the qwen_mtp_gguf_pipeline.py script. Manipulation of the weight_map argument can lead to path traversal, potentially exploitable remotely. The project uses a rolling release system, so specific affected or fixed versions are not disclosed. The vulnerability has a medium severity score of 5.1 and public exploit code is available. The vendor has been informed but has not yet responded or issued a fix.
CVE-2025-60490 is a heap use-after-free vulnerability in the gf_filter_pid_send_event_downstream function of GPAC Project/MP4Box before version 2.5. This flaw allows attackers to cause a denial of service (DoS) by supplying a specially crafted MP4 file. The issue is fixed in version 2.5.