Skip to content
PHP Security Reporting Policy Published on GitHub

PHP Security Reporting Policy Published on GitHub

First seen 22 Nov 2026, 09:13 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 09:13 UTC
  • •The PHP project asks researchers to report vulnerabilities privately via GitHub's form or [email protected].
  • •Reports stay private until published, and reporters are credited under the MITRE Credit System.
  • •Untrusted code execution and malicious-argument issues in functions not designed for unsanitized input are excluded as security issues.
  • •The sources describe reporting policy only and name no specific vulnerability or CVE.

The php-src repository on GitHub hosts a SECURITY.md file and a Security page that instruct researchers to report PHP vulnerabilities privately via GitHub's reporting form or by emailing [email protected]. The policy states that reports remain private until published, after which reporters are credited under the MITRE Credit System. The documents list issue categories that the PHP project does not consider security vulnerabilities, including memory violations caused by malicious error handlers, destructors, or __toString() functions, on the basis that PHP does not provide sandboxing and executing untrusted code is always considered unsafe. They also exclude passing malicious arguments to functions not intended to receive unsanitized input, such as mysqli_query(), while stating that escapeshellarg() should be hardened against unsafe inputs. The Security page is dated 2026-11-20 and the SECURITY.md page 2026-11-22. Neither article describes a specific vulnerability, CVE, exploitation, or affected version range.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 11h ago How this analysis works

Timeline

2026-11-20
PHP Security page published on GitHub
The php-src Security page sets out the private reporting process and lists issue types not considered security vulnerabilities.
github.com
2026-11-22
SECURITY.md reporting policy published
The php-src SECURITY.md file restates the private reporting channels and the MITRE Credit System crediting practice.
github.com

More articles in this cluster (2)

Common questions

How should a researcher report a PHP vulnerability?
Use the private reporting form on GitHub at the php-src repository, or email [email protected] if the form cannot be used or the issue is not a bug report.
Are reports made public?
Vulnerability reports remain private until published, and reporters are credited as contributors under the MITRE Credit System when they are published.
Which behaviours does PHP exclude from security issues?
The policy excludes malicious code causing memory violations through error handlers, destructors, or __toString() functions, and malicious arguments passed to functions not intended for unsanitized input, such as mysqli_query().