Advisory Database
  • Advisories
  • Dependency Scanning
  1. composer
  2. ›
  3. froxlor/froxlor
  4. ›
  5. CVE-2026-41236

CVE-2026-41236: Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path

May 29, 2026

Froxlor 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.

References

  • github.com/advisories/GHSA-mq5v-pxpm-8jw2
  • github.com/froxlor/froxlor/security/advisories/GHSA-mq5v-pxpm-8jw2
  • nvd.nist.gov/vuln/detail/CVE-2026-41236

Code Behaviors & Features

Detect and mitigate CVE-2026-41236 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 2.3.6 before 2.3.7

Fixed versions

  • 2.3.7

Solution

Upgrade to version 2.3.7 or above.

Impact 8.8 HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-59: Improper Link Resolution Before File Access ('Link Following')

Source file

packagist/froxlor/froxlor/CVE-2026-41236.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 06 Jun 2026 00:17:00 +0000.