Froxlor has privilege escalation in SSH key synchronization via symlinked authorized_keys path

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-41236: 0.37% estimated exploitation activity in the next 30 days; percentile 30.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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/authorizedkeys 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/authorizedkeys with a symlink to /root/.ssh/authorizedkeys. 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. Details The customer-facing SSH key workflow accepts an FTP user selection and an arbitrary public key from the authenticated session and forwards them into SshKeys::add(): On the server side, the add handler stores the public key and schedules an NSS rebuild as long as the customer has shell capability enabled at the…

Published by the source

29 May 2026, 15:40 UTC

Last modified by the source

9 Jun 2026, 11:54 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mq5v-pxpm-8jw2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41236

Advisory: Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path
IDs: CVE-2026-41236, GHSA-mq5v-pxpm-8jw2
Record: https://patchnext.com/advisories/cve-2026-41236 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: froxlor/froxlor 2.3.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist froxlor/froxlor: affected >= 2.3.6, <= 2.3.6; fixed in 2.3.7

## Suggested inspection (read-only)
- Packagist froxlor/froxlor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on froxlor/froxlor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mq5v-pxpm-8jw2 (GitHub-reviewed advisory GHSA-mq5v-pxpm-8jw2 lists affected ranges: Packagist froxlor/froxlor >=2.3.6 <=2.3.6)

Commands are suggestions: review each one before running it.