# CVE-2026-116013: OpenResty lua-resty-dns before 0.24 Denial of Service via DNS Response Parsing


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116013, GHSA-879w-j376-3fgq, UBUNTU-CVE-2026-116013

## What is CVE-2026-116013?

CVE-2026-116013 is a medium-severity vulnerability in openresty lua-resty-dns, published on 24 Oct 2026. 

### Official description

OpenResty lua-resty-dns before 0.24 contains an improper input validation vulnerability in parse_section() and _decode_name() that fails to check resource record lengths against the received message. Attackers controlling or spoofing a queried nameserver can send truncated record headers or RDATA, raising uncaught Lua exceptions in resolver:query() that abort requests and break name resolution.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

## Which versions are affected by CVE-2026-116013?


## How do I fix CVE-2026-116013?

No fix has been published for CVE-2026-116013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116013 being exploited?

There is no known exploitation of CVE-2026-116013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116013 and fix it if it is affected.

What it is: CVE-2026-116013 is a medium-severity vulnerability in openresty lua-resty-dns, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116013 in the wild and no public exploit code.

Affected product: openresty lua-resty-dns. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116013/ (Markdown: https://insights.sbomify.com/CVE-2026-116013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116013
- OSV: https://osv.dev/vulnerability/CVE-2026-116013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116013/
Summaries are generated and may contain mistakes; the official description above is the record.