Quick answers
- Is CVE-2026-90937 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90937 being exploited in the wild.
- How severe is CVE-2026-90937?
- Critical severity, with a CVSS score of 9.9, published 14 September 2026.
- Which products and versions are affected?
- Froxlor before 2.2.5.
- Is there a fix for CVE-2026-90937?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90937 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-90937?
- Check whether you run Froxlor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
froxlor contains a CRLF injection vulnerability (CWE-93) in the subdomain management API and UI. When customers create or update a subdomain redirect, the redirect URL is validated only for correct scheme and hostname, but the path component is not checked for newline characters (0x0A). The unvalidated URL is later written verbatim into nginx and Apache vhost configuration files during the cron rebuild cycle. An authenticated customer with subdomain modification rights can supply a URL containing literal newlines (e.g., http://attacker.com/path%0Ainjected_config) to break out of the current configuration directive and inject arbitrary nginx or Apache directives. This enables configuration corruption, denial of service by introducing syntax errors, hijacking of HTTP responses across other domains, and potential exposure of sensitive files via nginx include directives. Patches are available in version 2.2.5 and later.
Affected products
- froxlor froxlor before 2.2.5
Timeline
- 2026-06-29: disclosed
- 2026-09-14: advisory