nday
CVE-2026-116566

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

Python Software Foundation / CPython

Technical analysis appeared on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

adjacent network
AV:A in CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N (CVSS 4.0) from the CNA PSF
Python (CPython)
affected products in the CVE record: Python Software Foundation · CPython
open-source library / framework
affected products in the CVE record: Python Software Foundation · CPythonthe product type of Python (CPython) in nday's product registry
stage
ANA
disclosed
cvss
5.3 MEDIUM v4.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
10-29T17:45Z
PATpatch
no record yet
ANAanalysis
10-29T17:56Z
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:A
Adjacent: only from a nearby network, such as the same LAN segment or Bluetooth range
Attack complexity AC:L
Low: no target-specific security measures to get around
Attack requirements AT:P
Present: success depends on specific deployment or execution conditions, such as a race condition, a non-default setting or a position on the network path
Privileges required PR:H
High: administrative or similar privileges
User interaction UI:P
Passive: limited, involuntary interaction, such as visiting a page

CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 4.0 vector from the CVE record, scored by the CNA PSF.

Event log

+DISdisclosed

CVE record published by PSF. CVSS 5.3, medium.

src cvelist · nday , bulk import · raw
{
  "id": 467328,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-116566",
  "occurred_at": "2026-10-29T17:45:47.583Z",
  "observed_at": "2026-11-13T05:40:28.066817Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
      "version": "4.0",
      "base_score": 5.3,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-10-30T17:18:00.445284Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-29T17:45:47.583Z",
    "assigner_short_name": "PSF"
  }
}
+ANAtechnical analysis

Posted to the oss-security mailing list: “CPython [CVE-2026-116566] socket.getaddrinfo() accepts embedded null bytes in host and port”.

src osssec 2026/q4/436 · nday , observed live · raw
{
  "id": 496020,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/436",
  "occurred_at": "2026-10-29T17:56:51Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/436",
  "detail": {
    "list": "oss-security",
    "author": "Alan Coopersmith",
    "subject": "CPython [CVE-2026-116566] socket.getaddrinfo() accepts embedded null bytes in host and port",
    "is_reply": false
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.