PHP Security Reporting Policy Published on GitHub
Article Content
- •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.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Common questions
How should a researcher report a PHP vulnerability?
Are reports made public?
Which behaviours does PHP exclude from security issues?
Continue Reading
Critical Apache Roller RCE Vulnerability Actively Exploited in the Wild Apache has issued a warning regarding a critical remote code execution (RCE) vulnerability in Apache Roller, tracked as CVE-2026-129448, which is actively being exploited. This flaw affects versions 4.0.0 through 6.1.4 and allows unauthenticated attackers to execute arbitrary code via the XML-RPC endpoint. The…