# CVE-2025-8283: containers netavark DNS resolution confusion in Podman

Source: https://junglewise.ai/threats/cve-2025-8283-containers-netavark-dns-resolution-confusion-in-podman  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-07-28. Updated: 2026-06-04  
License: CC BY 4.0 with a link back

CVE-2025-8283 · Severity: low · CVSS 3.7 · Published 2025-07-28

A configuration issue in Netavark, a networking tool used by Podman to manage container connections, could cause containers to connect to the wrong servers. If a container is given a name that matches a real website or external server, the system might mistakenly route traffic to that external server instead of the intended internal container. This could lead to sensitive data being sent to an unauthorized third party or cause service disruptions.

Vendors: [crates.io](https://junglewise.ai/threats/vendors/crates-io).

## Quick answers

**Is CVE-2025-8283 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-8283 being exploited in the wild.

**How severe is CVE-2025-8283?** Low severity, with a CVSS score of 3.7, published 28 July 2025.

**Which products and versions are affected?** netavark (crates.io) < 1.15.1, SEMVER:introduced=0,fixed=1.15.1.

**Is there a fix for CVE-2025-8283?** Yes. netavark (crates.io): upgrade to 1.15.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-8283 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2025-8283?** Check whether you run netavark (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- netavark (crates.io): upgrade to 1.15.1 or later

  ```sh
  cargo update -p netavark
  ```


## Technical details

A vulnerability exists in Netavark due to the removal of the 'dns.podman' search domain in favor of using the host's 'resolv.conf'. When a container is created with a specific hostname, the DNS resolver may attempt to look up that name using the host's search domains. If an external server exists with a matching name within those search domains and returns a valid A/AAAA record, Netavark may forward traffic to that external entity instead of the local container. This is classified as a DNS resolution confusion (CWE-15) and is triggered when container names collide with external domain names present in the host's search path. The issue is fixed in Netavark version 1.15.1 by restoring the default Podman search domain.

## Affected products

- containers netavark < 1.15.1

## Identifiers

- CVE-2025-8283
- GHSA-rpcf-rmh6-42xr

## Timeline

- 2025-05-27: patched: Fix merged in upstream pull request #1256
- 2025-07-28: disclosed: CVE-2025-8283 published
- 2025-07-28: advisory: GitHub Advisory GHSA-rpcf-rmh6-42xr published

## References

- [https://access.redhat.com/security/cve/CVE-2025-8283](https://access.redhat.com/security/cve/CVE-2025-8283)
- [https://bugzilla.redhat.com/show_bug.cgi?id=2383941](https://bugzilla.redhat.com/show_bug.cgi?id=2383941)
- [https://github.com/containers/podman/issues/26198](https://github.com/containers/podman/issues/26198)
- [https://github.com/containers/netavark/pull/1256](https://github.com/containers/netavark/pull/1256)
- [https://github.com/containers/netavark/commit/068abc869b736a03a947b5419c102da73830e882](https://github.com/containers/netavark/commit/068abc869b736a03a947b5419c102da73830e882)

## Related threats

- [Containers Aardvark-dns infinite loop via malformed TCP DNS query](https://junglewise.ai/threats/cve-2026-35406-containers-aardvark-dns-infinite-loop-via-malformed-tcp-dns-query)