CVE-2026-41236

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: 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. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to ~/.ssh/authorized_keys under a customer-controlled home directory without verifying that the target path is not a symbolic link. If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace ~/.ssh/authorized_keys with a symlink to /root/.ssh/authorized_keys. When Froxlor's privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root's authorized key file, resulting in root SSH access. Version 2.3.7 contains a patch.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
28.8%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 8, 2026

Advisory Details (2)

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

Privilege escalation in SSH key synchronization via symlinked `authorized_keys` path · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-mq5v-pxpm-8jw2

Vendor Advisories for CVE-2026-41236(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/froxlor2.3.62.3.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 62× 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 112 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41236?
CVE-2026-41236 is a high vulnerability published on May 29, 2026. Froxlor is open source server administration software. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to ~/.ssh/authorizedkeys under a customer-controlled home directory without…
When was CVE-2026-41236 disclosed?
CVE-2026-41236 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41236 actively exploited?
CVE-2026-41236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41236?
CVE-2026-41236 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-41236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41236, 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-41236

Explore →

Is Your Infrastructure Affected by CVE-2026-41236?

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

Start Free Scan →Browse All CVEs