CVE-2026-41237 is a high-severity security vulnerability in froxlor/froxlor (composer), affecting versions <= 2.3.6. It is fixed in 2.3.7.
Summary The LOC record regex uses \s+ which matches newlines (allowing embedded newlines to pass), TLSA matchingType=0 has no upper bound on hex data length, and all validators return raw input without zone-file escaping. Affected Package Ecosystem: Other Package: froxlor Affected versions: all versions before fix commit b34829262dc3 Patched versions: >= commit b34829262dc3 Severity Medium -- CVSS CWE CWE-74 -- Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection) Details DNS record content is concatenated directly into bind9 zone files at DnsEntry.php line 83. Before the fix, LOC/RP/SSHFP/TLSA records had no content validation at all, enabling zone file injection via embedded newlines. The fix adds format-specific regexes and field validation but has gaps: the LOC regex's \s+ matches newlines in PHP's PCRE engine, allowing a LOC record with a newline between fields to pass validation but produce multiple lines in the zone file. TLSA matchingType=0 only requires len(data) >= 2 with no upper bound, enabling arbitrarily large payloads. All validators return raw input without zone-file escaping. PoC Steps to reproduce: git clone https://github.com/froxlor/froxlor /tmp/froxlortest cd /tmp/froxlortest && git checkout b34829262dc3~1 python3 poc.py Expected output: Impact An authenticated froxlor user with DNS management permissions can inject arbitrary records into bind9 zone files, enabling domain hijacking, phishing, or DNS amplification attacks via unbounded TLSA payloads. Suggested Remediation Replace \s+ in the LOC regex with [ \t]+ to exclude newlines. Add a maximum length for TLSA matchingType=0 data. Escape or reject newlines in all DNS record content before writing to zone files. Resources Incomplete fix commit: https://github.com/froxlor/froxlor/commit/b34829262dc3 Original CVE: CVE-2026-30932
composer
froxlor/froxlor (<= 2.3.6)froxlor/froxlor → 2.3.7 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-41237 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-41237 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-41237 in your environment →Upgrade froxlor/froxlor to 2.3.7 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-41237 is a high-severity security vulnerability in froxlor/froxlor (composer), affecting versions <= 2.3.6. It is fixed in 2.3.7.
froxlor/froxlor (composer) versions <= 2.3.6 is affected.
Yes. CVE-2026-41237 is fixed in 2.3.7. Upgrade to this version or later.
Whether CVE-2026-41237 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade froxlor/froxlor to 2.3.7 or later.