ALPINE-CVE-2026-129292: XSS

Published Nov 19, 2026
·
Updated

PHP-FPM status endpoint XSS via unescaped user and script fields.

The PHP-FPM full status output includes the request method, authentication user and script filename of each worker without escaping them for the HTML, XML or JSON format. When the status endpoint is enabled, an unauthenticated remote attacker can store markup in a worker's scoreboard entry with an ordinary request, for example through the username of an HTTP Basic authentication header that the web server forwards to PHP-FPM, or through the script filename where the attacker can influence it. When a user views the full status page as HTML, the injected JavaScript runs in the origin of that page. The attacker does not need access to the status endpoint. Malformed XML or JSON output can also disrupt monitoring tools.

This issue affects PHP versions before 8.2.36, 8.3. before 8.3.37, 8.4. before 8.4.28 and 8.5. before 8.5.13.

Affected Software

3 affected componentsFixes available
alpine/php83<8.3.37-r0
8.3.37-r0
alpine/php84<8.4.28-r0
8.4.28-r0
alpine/php85<8.5.13-r0
8.5.13-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/php83 to a version that resolves this vulnerability.

    Fixed in 8.3.37-r0
  2. Upgrade

    Upgrade alpine/php84 to a version that resolves this vulnerability.

    Fixed in 8.4.28-r0
  3. Upgrade

    Upgrade alpine/php85 to a version that resolves this vulnerability.

    Fixed in 8.5.13-r0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.2.36
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.3.37
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.4.28
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.5.13

Event History

Nov 19, 2026
CVE Published
via OSV·03:17 PM
Data Sourced
via OSV·03:17 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to the cross-site scripting risk?

Deployments are exposed when the PHP-FPM status endpoint is enabled and a user can view its full status output as HTML. The attacker does not need access to the status endpoint itself, but must be able to cause a request field forwarded to PHP-FPM, such as an HTTP Basic authentication username or an influenceable script filename, to contain markup.

2

Are default PHP-FPM configurations affected?

The issue requires the status endpoint to be enabled, so it does not apply where that endpoint is not enabled. HTML execution additionally requires someone to view the full status page in HTML format.

3

What can be done if an upgrade cannot be applied immediately?

Disable the PHP-FPM status endpoint if it is not required. If it must remain enabled, restrict access to the full status page and avoid exposing it as HTML; malformed XML or JSON output may still disrupt monitoring tools.

4

Which PHP versions need remediation?

Affected versions are PHP releases before 8.2.36, 8.3 releases before 8.3.37, 8.4 releases before 8.4.28, and 8.5 releases before 8.5.13. The listed Alpine packages are alpine/php83, alpine/php84, and alpine/php85.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203