Container data disclosure via DNS search-domain collision
Published Jul 28, 2025 · Updated Sep 1, 2026
DNS resolution confusion in Containers Netavark before 1.15.1 allows remote attackers to receive container traffic via hostname collisions. The bridge driver omits dns.podman from response.dns_search_domains, so container resolvers consult host search domains for matching hostnames. Exploitation requires control of a configured search domain plus knowledge of container names and connections; successful TLS validation blocks mismatched endpoints.
Summary
What happened
DNS resolution confusion in Containers Netavark before 1.15.1 allows remote attackers to receive container traffic via hostname collisions. The bridge driver omits dns.podman from response.dns_search_domains, so container resolvers consult host search domains for matching hostnames. Exploitation requires control of a configured search domain plus knowledge of container names and connections; successful TLS validation blocks mismatched endpoints.
The record
- CVE
- CVE-2025-8283
- Published
- Jul 28, 2025
- Updated
- Sep 1, 2026
- Vendor
- Containers
- Product
- Netavark
- Classifications
- CWE-15, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 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=0 <1.15.1
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