DNS cache poisoning via predictable resolver identifiers
Published Apr 7, 2026 · Updated Apr 7, 2026
DNS cache poisoning in Erlang/OTP 17.0 and later affected releases allows remote attackers to forge resolver answers over UDP. inet_res assigns sequential process-global 16-bit transaction IDs, reuses predictable source-port behavior, and validates replies primarily against the identifier. Exploitation requires an application to configure DNS lookup or call inet_res directly and an attacker to observe or predict an identifier; native OS resolution is unaffected by default.
Summary
What happened
DNS cache poisoning in Erlang/OTP 17.0 and later affected releases allows remote attackers to forge resolver answers over UDP. inet_res assigns sequential process-global 16-bit transaction IDs, reuses predictable source-port behavior, and validates replies primarily against the identifier. Exploitation requires an application to configure DNS lookup or call inet_res directly and an attacker to observe or predict an identifier; native OS resolution is unaffected by default.
The record
- CVE
- CVE-2026-28810
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- Erlang
- Product
- Erlang/OTP
- Classifications
- CWE-340, CAPEC-142
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=07b8f441ca711f9812fad9e9115bab3c3aa92f79 <* changes=[{"at":"36f23c9d2cc54afe83671dd7343596d7972839a5","status":"unaffected"},{"at":"dd15e8eb03548c5e55e9915f0e91389ec6bad9fd","status":"unaffected"},{"at":"b057a9d995017b1be50d6dc02edd52382f3231b8","status":"unaffected"}]
- Affected versionversion=17.0 <* changes=[{"at":"28.4.2","status":"unaffected"},{"at":"27.3.4.10","status":"unaffected"},{"at":"26.2.5.19","status":"unaffected"}]
- Affected versionversion=3.0 <* changes=[{"at":"10.6.2","status":"unaffected"},{"at":"10.2.7.4","status":"unaffected"},{"at":"9.2.4.11","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo