CVE-2026-116566: socket.getaddrinfo() accepts embedded null bytes in host and port

Published Oct 29, 2026
·
Updated

socket.getaddrinfo() previously accepted null bytes within host and port parameters which can cause the values to be silently truncated.

Event History

Oct 29, 2026
CVE Published
via MITRE·05:45 PM
Advisory Published
via OSV·05:45 PM
Data Sourced
via MITRE·05:45 PM
DescriptionWeakness
Data Sourced
via OSV·05:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What conditions are required to exploit this issue?

An attacker must be able to influence a host or port value passed to socket.getaddrinfo(), including supplying an embedded null byte. The vulnerable call then silently truncates the value at the null byte.

2

Who is most likely to be exposed?

Applications that pass attacker-controlled hostnames or port values to socket.getaddrinfo() are the relevant exposure. The supplied data does not identify particular products, deployments, or default configurations as affected.

3

How can I determine whether my application may be affected?

Review uses of socket.getaddrinfo() and trace whether the host or port arguments can contain untrusted input. Inputs containing embedded null bytes are the specific condition to test for, because they may be resolved using only the portion before the null byte.

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