Skip to content
Fencer Intel
low 3.4

CVE-2025-52889 json

Incus vulnerable to DoS through antispoofing nftables firewall rule bypass on bridge networks with ACLs

published last yr. modified 4mo ago also EUVD-2025-19115 , GHSA-9q7c-qmhm-jv86 , GO-2025-3781

cvss
3.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

Incus is a system container and virtual machine manager. When using an ACL on a device connected to a bridge, Incus version 6.12 and 6.13 generates nftables rules for local services (DHCP, DNS...) that partially bypass security options `security.mac_filtering`, `security.ipv4_filtering` and `security.ipv6_filtering`. This can lead to DHCP pool exhaustion and opens the door for other attacks. A patch is available at commit 2516fb19ad8428454cb4edfe70c0a5f0dc1da214.

Patch / fix

  • go github.com/lxc/incus/v6 6.14.0
  • linuxcontainers incus 6.14
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1
  • incus openSUSE Tumbleweed 6.14-1.1

opensuse advisories openSUSE-SU-2025:15405-1openSUSE-SU-2025:15317-1

  • incus-feature Alpine 3.24, Alpine 3.23 6.14.0-r0

alpine advisories ALPINE-CVE-2025-52889

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-52889 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-52889 updated cvss 3.4

incus: Incus denial of service

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/lxc/incus/security/advisories/GHSA-9q7c-qmhm-jv86 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.4 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L
GitHub 3.1 3.4 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/lxc/incus/v6
<6.14.0
>=6.12.0, <6.14.0
6.14.0
go github.com/lxc/incus
all versions
 no fix listed

Affected products

  • lxc incus

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.