DEBIAN-CVE-2026-123125: SSRF

Published Nov 5, 2026
·
Updated

The Symfony Validator component IpValidator incompletely classifies internal addresses in the filtered modes of the Ip constraint, so some internal addresses are accepted as public, which can lead to Server-Side Request Forgery (SSRF) in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11. In these modes, IpValidator relies on the PHP flags FILTERFLAGNOPRIVRANGE and FILTERFLAGNORESRANGE to classify addresses as public, private, or reserved. These flags do not cover shared address space (100.64.0.0/10) or IPv4-mapped, IPv4-compatible, and 6to4 IPv6 addresses, which can embed internal IPv4 addresses. A value such as ::ffff:127.0.0.1 can therefore pass validation even though it points to an internal host. Applications that rely on the Ip constraint to reject internal addresses, for example before making a server-side request to a user-supplied address, can be exposed to SSRF.

Affected Software

3 affected components
debian/symfony*
debian/symfony*
debian/symfony*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade symfony/validator to a version that resolves this vulnerability.

    Fixed in 5.4.56
  2. Upgrade

    Upgrade symfony/validator to a version that resolves this vulnerability.

    Fixed in 6.4.50
  3. Upgrade

    Upgrade symfony/validator to a version that resolves this vulnerability.

    Fixed in 7.4.23
  4. Upgrade

    Upgrade symfony/validator to a version that resolves this vulnerability.

    Fixed in 8.1.11

Event History

Nov 5, 2026
CVE Published
via OSV·04:17 PM
Data Sourced
via OSV·04:17 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are exposed to exploitation?

Applications are exposed when they use Symfony's Ip constraint in filtered modes to reject internal addresses and then make a server-side request to a user-supplied address. The issue can allow addresses such as ::ffff:127.0.0.1 to be accepted as public even though they resolve to an internal target.

2

What address forms can bypass the intended internal-address filtering?

The affected PHP filter flags do not cover shared address space 100.64.0.0/10, IPv4-mapped IPv6 addresses, IPv4-compatible IPv6 addresses, or 6to4 IPv6 addresses that embed internal IPv4 addresses.

3

Are all Symfony versions affected?

Affected versions are Symfony releases before 5.4.56, 6.x before 6.4.50, 7.x before 7.4.23, and 8.x before 8.1.11. The provided data does not identify whether a particular application uses the vulnerable filtered Ip constraint modes.

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