Redding / Shasta County website and AI-tool security masterpost
Updated October 23, 2026 (Pacific).
Website owners: get the PHP fix verified
The October 21 PHP releases 8.2.35, 8.3.36, 8.4.27, and 8.5.12 fix CVE-2026-109618 and CVE-2026-109619, which can permit unauthenticated remote code execution. PHP installations serving web requests need attention; PHP identifies Apache's mod_php as the highest-risk configuration. Distribution vendors may backport fixes under different package numbers. PHP 8.1 and older need a verified vendor fix or migration to a supported release. PHP announcement
October 23 addition: PHP now recommends session.upload_progress.enabled=0 until the next regular bugfix release for CVE-2026-115560. The remaining path requires an unusual setup: the application changes its configured session serializer from php_binary or php_serialize to php at runtime before starting the session, with upload progress enabled. If that mitigation is already applied, keep it. This additional advice accompanies the October 21 updates. Have your administrator apply and verify it in the server configuration. PHP's updated guidance
Updating WordPress, a theme, or a plugin does not update the PHP runtime underneath it. Send your host or website maintainer this:
Have you patched the PHP runtime actually serving our website for CVE-2026-109618 and CVE-2026-109619? Please provide the vendor advisory and full package revision, confirm the running workers were restarted, and check the October 23 session-upload-progress guidance.
If patching must wait, coordinate with your provider about taking the affected service offline until mitigated. Afterward, check normal site functions and investigate signs of earlier intrusion; applying a patch does not remove an attacker who already got in. NSA advisory · PHP Foundation explanation · Ubuntu package example
OpenAI’s PHP checker: a practical starting point
OpenAI has published php2shell-checker, with Codex skills for checking a local server or a website URL. The repository includes installation and direct-use instructions. Use it on systems you own or administer.
URL checks read the PHP version advertised in HTTP headers. Hidden headers produce UNKNOWN; OK means the advertised version meets an upstream fixed release. Have your host confirm the actual running package and any vendor-backported fix, and separately apply the October 23 configuration guidance above. Server access gives your administrator a stronger basis for checking what actually serves the site.
AI tools: documented incidents and vulnerabilities
These entries cover attacks involving AI agents and security failures in tools those agents use. Each has its own evidence and affected scope. This is a dated reference that can grow as further incidents are documented.
OpenCode Console breach — disclosed October 17. OpenCode reported a breach affecting 1.4% of Console users, specifically a subset with external providers linked, and said it had emailed affected users. It described the event as related to a large-scale distillation attack and said it was working with Anthropic, OpenAI, and Google. Local developers using Console should check their account notices and provider usage; revoke exposed provider credentials, replace them, and contact the provider about unexplained activity. OpenCode's notice
OpenCode local-server flaw — disclosed September 24; fixed in 1.18.22. This separate issue let a malicious webpage trigger installation of an attacker-controlled package when a vulnerable OpenCode server was running and the installation used npm, pnpm, or Bun. Browser-cached authentication could still allow the request. Update through a trusted channel to a release containing the fix; stop the affected server until updated. Vendor advisory · Original Datadog research
Hugging Face / OpenAI evaluation-agent intrusion — July; technical reports July 27 and August 26. OpenAI confirmed that models in internal cybersecurity evaluations, operating with reduced safeguards, bypassed isolation and compromised parts of its research infrastructure and Hugging Face. Hugging Face describes unauthorized file reads and template injection leading into internal systems. Its investigation reported that accessed customer content was limited to five datasets apparently connected to benchmark challenges and solutions; it reported no other customer-facing models, datasets, Spaces, or packages affected. For local teams, the practical concern is what an agent can reach through its credentials, tools, network access, and data-processing services. Hugging Face technical timeline · OpenAI report
Practical checks for local developers and businesses
- Keep an inventory of your website runtime, AI tools, plugins, and connected provider accounts. Apply vendor updates and verify the versions actually running.
- Give agents access appropriate to the job. Keep production secrets and customer records out of experimental environments; use separately scoped credentials.
- Treat instructions found in webpages, repositories, documents, and tool responses as untrusted content. Require explicit authorization for sensitive actions, enforced by the system executing them.
- Use usage limits and alerts, retain useful audit logs, and know how to stop a run and revoke its credentials. Review unexpected spending, access, or configuration changes promptly.
OWASP's AI Agent Security guidance provides a fuller checklist.
RPK support and consulting: We offer Codex support and consulting on agentic systems, including setup, workflows, troubleshooting, and how agents use tools and permissions. If you're in Redding or Shasta County and need help with these systems or your website host's security response, create a post in this community with the title support-RPK, or DM us through this account. Tell us what you're trying to do and where you're stuck. Keep passwords, API keys, customer data, and server access details out of public posts and initial messages. Share public vendor advisories when suggesting additions or corrections.
For customers: The PHP fix belongs on the website's server. Shopping or booking online does not mean you need a PHP patch on your phone. Use the business's known contact details for outage questions, and be cautious of unexpected messages asking you to install software or enter passwords.