Skip to content

Add PHP2Shell vulnerabilities page - #545

Open
hnyasingunaydin wants to merge 1 commit into
ByteInternet:masterfrom
hnyasingunaydin:security-php2shell-cve-2026-109618
Open

hnyasingunaydin wants to merge 1 commit into
ByteInternet:masterfrom
hnyasingunaydin:security-php2shell-cve-2026-109618

Conversation

@hnyasingunaydin

Copy link
Copy Markdown
Contributor

Summary

Adds a new page under Best Practices → Security: PHP2Shell: Critical PHP Vulnerabilities (CVE-2026-109618, CVE-2026-109619 and CVE-2026-115560).

The page covers:

  • What happened, how the vulnerabilities work and how likely an attack is
  • Which PHP versions are affected
  • What Hypernode did during the emergency maintenance on 21 October 2026
  • How to check the PHP build date
  • The narrower CVE-2026-115560 and how to check for runtime changes of session.serialize_handler
  • What customers should do, with links to the PHP version, eComscan and recovery guides

Based on the PHP security advisory, the PHP release notes, and the Sansec PHP2Shell analysis.

Explain the PHP2Shell vulnerabilities (CVE-2026-109618, CVE-2026-109619)
and CVE-2026-115560, what Hypernode did, and what customers should check.

Co-authored-by: yasingunaydiin <81875281+yasingunaydiin@users.noreply.github.com>
@hnyasingunaydin
hnyasingunaydin force-pushed the security-php2shell-cve-2026-109618 branch from 48c397e to ff8685e Compare November 7, 2026 11:46
Comment on lines +7 to +8
title: 'PHP2Shell: Critical PHP Vulnerabilities (CVE-2026-109618, CVE-2026-109619
and CVE-2026-115560) | Security | Hypernode'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: 'PHP2Shell: Critical PHP Vulnerabilities (CVE-2026-109618, CVE-2026-109619
and CVE-2026-115560) | Security | Hypernode'
title: 'PHP2Shell: Critical PHP Vulnerabilities (CVE-2026-109618, CVE-2026-109619
and CVE-2026-115560)'

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants