CVE-2026-123119: Symfony: NoPrivateNetworkHttpClient Does Not Pin the Checked IP of Cached Hosts, Letting DNS Rebinding Enumerate Internal Ports (Incomplete Fix for CVE-2024-50342)

Published Nov 5, 2026
·
Updated

The Symfony HttpClient component NoPrivateNetworkHttpClient does not pin the checked IP address of cached hosts, allowing for DNS rebinding to bypass private network restrictions, resulting in enumeration of internal hosts and ports 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.

NoPrivateNetworkHttpClient resolves the host of each request and checks the IP before connecting. It caches the result per host, and passes the IP to the decorated client through the resolve option so that the client connects to the exact IP that was checked. The issue is that resolve was only passed on the first lookup of a host: on subsequent requests, the decorated client resolved the host again on its own.

An attacker who controls a host's DNS can exploit this with DNS rebinding by answering the first lookup with a public IP, and subsequent lookups with a private IP, so when an application sends several requests to that host through the same client, the later requests connect to the private IP. This happens, for example, when an application fetches several URLs of a repository provided by a user. The check of the primaryip in the onprogress callback still aborts the request before anything is sent, but the connection is made, and the error differs depending on whether the port is open or closed. This allows enumerating internal hosts and ports, as in CVE-2024-50342.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Symfony HttpClient component to a version that resolves this vulnerability.

    Fixed in 5.4.56
  2. Upgrade

    Upgrade Symfony HttpClient component to a version that resolves this vulnerability.

    Fixed in 6.4.50
  3. Upgrade

    Upgrade Symfony HttpClient component to a version that resolves this vulnerability.

    Fixed in 7.4.23
  4. Upgrade

    Upgrade Symfony HttpClient component to a version that resolves this vulnerability.

    Fixed in 8.1.11

Event History

Nov 5, 2026
CVE Published
via MITRE·12:57 PM
Data Sourced
via MITRE·12:57 PM
DescriptionWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Applications using Symfony HttpClient's NoPrivateNetworkHttpClient are affected if they run versions earlier than 5.4.56, 6.4.50 within the 6.x line, 7.4.23 within the 7.x line, or 8.1.11 within the 8.x line.

2

What conditions are required for exploitation?

An attacker must control the DNS responses for a host and cause the application to make several requests to that host through the same client. The first DNS lookup must return a public IP address, while later lookups return a private IP address.

3

What is the practical impact of a successful attack?

Later requests can connect to a private IP address despite the private-network check, enabling enumeration of internal hosts and ports. One cited scenario is an application fetching several repository URLs supplied by a user.

4

What should be done to remediate the issue?

Upgrade to Symfony 5.4.56, 6.4.50, 7.4.23, or 8.1.11, as applicable to the deployed release line.

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