AI Science Tracker

Codex Security identifies a dnsmasq DNS-response bounds-check flaw

dnsmasq · AI involvement attributed to OpenAI Codex Security

Finding and attribution

OpenAI says Codex Security independently identified the vulnerable pattern associated with this CVE. The dnsmasq maintainer later released the fix in 2.92rel2.

Product: dnsmasq. AI system: OpenAI Codex Security. Team / organization: OpenAI.

CVE identifiers: CVE-2026-5172.

AI and human contribution (source account): OpenAI specifically lists CVE-2026-5172 among the four dnsmasq CVEs for which Codex Security independently identified vulnerable patterns; the maintainer confirms the remediation release.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The cited sources document the vulnerability and remediation; they do not claim exploitation in the wild.

Remediation status: fix documented. The maintainer announced the fix in dnsmasq 2.92rel2 on 2026-05-11. Package deployment is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 11 May 2026. AI attribution dated 22 Jun 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.5. Documented technical effects: other, denial of service.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-5172: other, denial of service.
Prerequisites / affected scope: A malformed DNS response can cause a heap out-of-bounds read in dnsmasq extract_addresses/extract_name and crash the process..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: The maintainer announced the fix in dnsmasq 2.92rel2 on 2026-05-11. Package deployment is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases