Add security warning about publicly exposed PHP-FPM - #5263
Open
lacatoire wants to merge 1 commit into
Open
Conversation
lacatoire
force-pushed
the
fix/fpm-security-warning
branch
2 times, most recently
from
August 21, 2026 10:00
520a3af to
58b3c13
Compare
lacatoire
force-pushed
the
fix/fpm-security-warning
branch
from
August 21, 2026 10:04
58b3c13 to
6d230ce
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<warning>block to the FPM main page (install/fpm/index.xml) about therisk of exposing PHP-FPM to untrusted networks (arbitrary code execution)
listen.allowed_clients, and Docker/container bestpractices
listendirective ininstall/fpm/configuration.xmlFixes #3984