Skip to content
Threat Brief

← All advisories

CVE-2026-116566

Medium 5.3No known exploitationFix available

socket.getaddrinfo() accepts embedded null bytes in host and port

Record last updated

CVSS score

5.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 18% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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

Weakness: CWE-158

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
mail.python.org (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 python3 3.12.14-2 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 python3 3.12.16-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 python3 3.12.16-2 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl4 python-py 1.11.0-22.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC
Python Software FoundationCPythonall versions before 3.16.03.16.0CVE Program

Timeline

  1. Disclosure

    CVE record published by PSF

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references