Bug 2512068 - CVE-2026-61477 libvirt: libvirt: newline injection in network XML DNS TXT/SRV fields allows dnsmasq config directive injection [fedora-all]
Summary: CVE-2026-61477 libvirt: libvirt: newline injection in network XML DNS TXT/SRV...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["f6be3186-f1c4-47fd-b381-1...
Depends On:
Blocks: CVE-2026-61477
TreeView+ depends on / blocked
 
Reported: 2026-08-06 14:36 UTC by Samuele Negrini
Modified: 2026-08-06 14:36 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Samuele Negrini 2026-08-06 14:36:46 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A flaw was found in libvirt. The network XML parser accepts XML numeric character references for line breaks (
 / 
) in DNS TXT record value attributes and SRV record domain/target attributes without sanitization. The network driver writes these values directly into the line-oriented dnsmasq configuration file as txt-record= or srv-host= directives. An embedded newline terminates the intended directive and begins a new one under attacker control (e.g., dhcp-script=/bin/sh -c '<cmd>'), which dnsmasq executes as root when the virtual network is started. Under the default libvirt deployment model, read-write access to the libvirt socket is already root-equivalent, and the <dnsmasq:options> raw namespace already provides a documented mechanism for arbitrary directive injection, making this a hardening issue only. However, under non-default polkit fine-grained access control configurations that grant only network.write and network.start permissions, this could represent a privilege boundary violation.


Note You need to log in before you can comment on or make changes to this bug.