photo sharing and upload picture albums photo forums search pictures popular photos photography help login
Tom Beech | all galleries >> Galleries >> Misc Sights > Just saw this post by Pbase about the troubles we have been seeing lately
previous | next

Just saw this post by Pbase about the troubles we have been seeing lately

this message was posted in "show and tell" that I never look at, seems this was their only option to speak on the subject given current disruption problems and removal of the other forums


other sizes: small medium large original auto
previous | next
share
Tom Beech18-Nov-2026 14:44
Sorry, I only know what I read about this subject, and this is what I'm reading;

Repeated HTTP 500 errors in PHP during late 2026 are a primary indicator of active exploitation attempts targeting the critical PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), or they can stem from an incomplete security patch or fatal memory exhaustion.

Why HTTP 500 Errors Occur

• Active Exploitation Attempts. Attackers trigger these flaws by forcing PHP out-of-memory conditions or fatal errors during file uploads. According to Nexcess, unusual file-upload requests followed by memory-limit errors or repeated HTTP 500 errors are key warning signs of an attack.

• Out-of-Memory Handling (CVE-2026-109618). When a malicious request hits the PHP memory limit, the allocation fails and leaves internal request data pointing to uninitialized memory. This causes the worker process to crash and return a 500 Internal Server Error during cleanup.

• Fatal Error Stale State (CVE-2026-109619). A fatal error during session upload progress leaves a global pointer referencing freed memory. Subsequent requests handled by the same PHP worker interact with this corrupted state, resulting in server crashes and 500 errors
.
• Post-Patch Configuration Issues. Applying emergency OS vendor updates or modifying php.ini settings (such as altering memory_limit or post_max_size as temporary mitigations) can cause legitimate scripts to exceed limits and throw 500 errors.

Immediate Troubleshooting & Remediation

• Update PHP Immediately. The PHP security team and Google Cloud advise upgrading to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35 as the only complete fix. If you run an end-of-life version like PHP 8.1 or older, check your OS vendor for backported security packages.

• Inspect Server Logs. Check your web server and PHP-FPM error logs for sudden spikes in memory exhaustion errors, malformed PHPSESSID cookies, or worker processes restarting unexpectedly.

• Apply Temporary Mitigations. If you cannot patch right away, community discussions on Reddit highlight disabling session.upload_progress.enabled in your php.ini and lowering post_max_size to block the primary attack vectors.

• Check for Compromise. Because these flaws allow unauthenticated remote code execution, audit your server for unauthorized files, unknown background processes, or unexpected outbound network connections if you see unexplained 500 errors in your logs
Tom Beech18-Nov-2026 14:27
From what I'm seeing, and IMO the PHP bug is causing all of our problems here at Pbase, however the main purpose of my post is to let members know that they are aware of problems as without the rest of the forum topics there is no way for us to let others know you are not alone with the fault.

Also, without the other forum topics, this post by them gives you Chuck Neel's (slug) Email address slug23@gmail.com
Rob Legeland18-Nov-2026 13:55
Thanks for sharing this message, Tom! However, as I understand it, PBase is referring specifically to the Show & Tell functionality rather than the website as a whole. I don't see anything here that explains the widespread Error 500 issues and other disruptions we've been experiencing across PBase lately. But perhaps I'm missing something?
pkocinski18-Nov-2026 13:05
I never knew about "show and tell" and I'll be glad when the ERROR 500 issue is resolved.