PHP2Shell: Emergency Fixes for PHP
Tech Weekly News Review – October 25 to November 1, 2026: PHP2Shell, AI Agent Security and Python’s Latest Developments
OpenWolf Tutorial: Improve AI Coding Agent Productivity and Project Management

Tech Weekly News Review – October 25 to November 1, 2026: PHP2Shell, AI Agent Security and Python’s Latest Developments

The week at a glance

Security dominates this week’s headlines, with PHP2Shell, two critical vulnerabilities exploited across exposed infrastructure, and several warnings about AI assistants capable of leaking secrets or following malicious instructions hidden in files. GitLab, Ivanti and Cisco are also affected by vulnerabilities added to exploited-vulnerability catalogs. On the AI front, falling model costs and the emergence of autonomous agents running directly on smartphones highlight the industry’s rapid transformation. Finally, Python is abandoning its experimental JIT compiler, while GitHub strengthens dependency controls for its workflows.

PHP2Shell: Servers compromised on a large scale

The vulnerabilities CVE-2026-109618 and CVE-2026-109619 can, under certain conditions, allow remote code execution without authentication. PHP versions earlier than 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are affected; PHP 8.1 and older versions require migration to a supported branch. Exploitation is no longer theoretical: Dream Research documents a campaign that compromised 25 servers, including government infrastructure, notably targeting Palo Alto PAN-OS 12.1 and 12.2 appliances running PHP 8.0.30. Administrators should apply both PHP and vendor security updates, then restart the affected processes.

AI agents: Your secrets are no longer safe in your repository

Development assistants are becoming a new attack surface. Experiments show that a simple log file containing malicious instructions can hijack the behaviour of several models. This is known as indirect prompt injection. Another issue is that secrets can be transmitted to AI assistants through test logs, environment variables or configuration snippets, without ever being committed to Git. Sensitive information must therefore be treated as exposed whenever it enters the context provided to an AI tool.

AI: Lower prices and autonomous agents

OpenAI and Anthropic’s API prices have fallen sharply, by up to 80% according to an analysis published this week. This makes applications that previously required substantial budgets much more affordable. Meanwhile, Mika illustrates another emerging trend: this open-source Android agent can interact directly with apps and the web from the device itself. Finally, a comparative study reminds us that an older specialised model can outperform general-purpose LLMs on a specific medical task: specialisation still matters.

Critical vulnerabilities: GitLab, Ivanti and Cisco under scrutiny

Several vulnerabilities have now been listed as actively exploited. CVE-2026-97229 allows unauthenticated code execution on GitLab CE/EE versions earlier than 19.2.8, 19.3.5 and 19.4.2; these patched versions should be installed. CVE-2026-118527 affects Ivanti Connect Secure, including versions earlier than 25.1.1.3, 25.1.3.1 and 22.8R2.6; apply the corresponding security updates. Finally, CVE-2026-76418 affects Cisco ASA and FTD in certain VPN configurations; Cisco has released patches for the affected branches. These appliances should be treated as high-priority maintenance targets.

Python abandons its experimental JIT

After several years of development, the CPython Just-In-Time (JIT) compiler project has suffered a major setback. PEP 836, intended to define the conditions for integrating this technology sustainably, was withdrawn on October 19. Maintainers were unable to establish a satisfactory framework for maintenance, compatibility and cross-platform support. This decision does not undermine Python itself, but highlights how difficult it can be to integrate such a complex optimisation into such a widely used ecosystem.

GitHub Actions: Locking dependencies is not enough

GitHub is introducing a lockfile mechanism for Actions workflows, allowing dependencies to be pinned to specific commits, including indirectly referenced dependencies. The goal is to prevent a later change to an external tag from silently changing the code executed during a deployment. However, locking a dependency does not guarantee that it is safe. Developers still need to review the actions they use, control updates and integrate scanning tools such as Trivy to detect vulnerabilities in Docker images.

Add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.