CVE-2026-41234 Froxlor: BIND Zone File Injection via TXT Record Content
Authenticated users can inject BIND directives into zone files via unsanitized TXT records, potentially leading to code execution or data modification.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41234?
CVE-2026-41234 is a high-severity code injection vulnerability in froxlor, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Froxlor is open source server administration software. Prior to version 2.3.7, the `DomainZones.add` API endpoint does not sanitize newline characters in TXT record content. An authenticated customer with DNS editing enabled can inject newlines into TXT record values, which break out of the record line in the generated BIND zone file. This enables injection of arbitrary BIND directives (`$INCLUDE`, `$GENERATE`) and arbitrary DNS records (A, MX, CNAME) into the zone file written to disk by the DNS rebuild cron. This is an incomplete fix for CVE-2026-30932 (GHSA-x6w6-2xwp-3jh6), which patched the same newline injection for LOC, RP, SSHFP, and TLSA record types but did not patch TXT records. Version 2.3.7 contains an updated patch.
Weakness: CWE-74
Which versions are affected by CVE-2026-41234?
2 open source packages ship an affected version, including froxlor/froxlor.
| Package | Affected | Fixed in |
|---|---|---|
froxlor/froxlor Packagist | All versions | 2.3.7 |
froxlor/froxlor Packagist | All versions | 2.3.7 |
How do I fix CVE-2026-41234?
Upgrade froxlor/froxlor to 2.3.7 or later.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2026-41234 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41234 exists.
Sources
Also known as GHSA-37m5-m4q3-fc6x.