CVE-2026-41234

HIGHPre-NVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.6
EG Score
7.6(medium)
EPSS
18.7%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 5, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_release.
github_release Patch Available

froxlor security release 2.3.7

Patch available: froxlor/froxlor 2.3.7

https://github.com/froxlor/froxlor/releases/tag/2.3.7
github Patch Available🟡 PoC Available

Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API · CVE-2026-30932 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-x6w6-2xwp-3jh6
github Patch Available🟡 PoC Available

BIND Zone File Injection via TXT Record Content · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-37m5-m4q3-fc6x

Vendor Advisories for CVE-2026-41234(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
froxlor/froxlor0.10.0 ... 2.3.6 (108 versions)2.3.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 113 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 15:12 UTCEG score recompute
  5. 2026-07-14 03:26 UTCEG score recompute
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 23:56 UTCEG score recompute
  11. 2026-07-11 12:35 UTCEG score recompute
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 06:36 UTCEG score recompute
  15. 2026-07-08 16:19 UTCEG score recompute
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-03 19:38 UTCEG score recompute
  25. 2026-07-02 19:14 UTCEG score recompute
Show 75 more
  1. 2026-07-02 07:54 UTCEG score recompute
  2. 2026-07-01 20:31 UTCEG score recompute
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 09:11 UTCEG score recompute
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 21:51 UTCEG score recompute
  7. 2026-06-29 22:46 UTCEG score recompute
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-29 11:26 UTCEG score recompute
  10. 2026-06-29 00:06 UTCEG score recompute
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 12:45 UTCEG score recompute
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 01:26 UTCEG score recompute
  15. 2026-06-27 14:06 UTCEG score recompute
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-27 02:44 UTCEG score recompute
  18. 2026-06-26 15:11 UTCEG score recompute
  19. 2026-06-25 20:56 UTCEG score recompute
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-25 09:36 UTCEG score recompute
  23. 2026-06-24 22:16 UTCEG score recompute
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-24 09:16 UTCEG score recompute
  26. 2026-06-23 21:33 UTCEPSS rescore
  27. 2026-06-23 18:59 UTCEG score recompute
  28. 2026-06-22 14:25 UTCEPSS rescore
  29. 2026-06-22 14:25 UTCEPSS rescore
  30. 2026-06-21 14:56 UTCEPSS rescore
  31. 2026-06-21 14:56 UTCEPSS rescore
  32. 2026-06-21 01:59 UTCEPSS rescore
  33. 2026-06-20 12:30 UTCEG score recompute
  34. 2026-06-19 20:33 UTCEG score recompute
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-19 04:28 UTCEG score recompute
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-18 16:30 UTCEG score recompute
  40. 2026-06-18 01:39 UTCEG score recompute
  41. 2026-06-17 17:53 UTCEPSS rescore
  42. 2026-06-17 14:19 UTCEG score recompute
  43. 2026-06-17 02:58 UTCEG score recompute
  44. 2026-06-16 17:52 UTCEPSS rescore
  45. 2026-06-16 15:38 UTCEG score recompute
  46. 2026-06-16 04:18 UTCEG score recompute
  47. 2026-06-15 17:49 UTCEPSS rescore
  48. 2026-06-15 16:53 UTCEG score recompute
  49. 2026-06-15 05:33 UTCEG score recompute
  50. 2026-06-14 18:13 UTCEG score recompute
  51. 2026-06-14 06:35 UTCEG score recompute
  52. 2026-06-13 23:00 UTCEPSS rescore
  53. 2026-06-13 19:15 UTCEG score recompute
  54. 2026-06-13 07:51 UTCEG score recompute
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-06-12 23:12 UTCEPSS rescore
  57. 2026-06-12 20:31 UTCEG score recompute
  58. 2026-06-12 09:10 UTCEG score recompute
  59. 2026-06-11 21:48 UTCEG score recompute
  60. 2026-06-11 14:00 UTCEPSS rescore
  61. 2026-06-11 10:29 UTCEG score recompute
  62. 2026-06-10 23:08 UTCEG score recompute
  63. 2026-06-10 22:18 UTCEPSS rescore
  64. 2026-06-10 13:22 UTCEPSS rescore
  65. 2026-06-10 13:22 UTCEPSS rescore
  66. 2026-06-10 11:48 UTCEG score recompute
  67. 2026-06-10 00:29 UTCEG score recompute
  68. 2026-06-09 13:09 UTCEG score recompute
  69. 2026-06-09 01:50 UTCEG score recompute
  70. 2026-06-08 14:29 UTCEG score recompute
  71. 2026-06-08 14:17 UTCEPSS rescore
  72. 2026-06-08 14:17 UTCEPSS rescore
  73. 2026-06-08 03:09 UTCEG score recompute
  74. 2026-06-07 15:50 UTCEG score recompute
  75. 2026-06-07 15:25 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41234?
CVE-2026-41234 is a high vulnerability published on June 3, 2026. 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…
When was CVE-2026-41234 disclosed?
CVE-2026-41234 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41234 actively exploited?
CVE-2026-41234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41234?
CVE-2026-41234 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-41234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41234, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41234

Explore →

Is Your Infrastructure Affected by CVE-2026-41234?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs