{"items":[{"id":"NVI-00008041","kind":"vulnerability","title":"Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mq5v-pxpm-8jw2","CVE-2026-41236"],"plain_summary":"GitHub lists this reviewed advisory for froxlor/froxlor. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.7 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-09T11:54:23.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-676b4fedaf283e5dc41a2ab2206e6e62"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.366%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.30649. Missing scores are unknown.","source_id":"sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-676b4fedaf283e5dc41a2ab2206e6e62","url":"https://github.com/advisories/GHSA-mq5v-pxpm-8jw2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mq5v-pxpm-8jw2","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T20:56:39.448Z"},{"id":"sr-f30c0c7d173bf7eda003cb2533bbf948","url":"https://github.com/advisories/GHSA-mq5v-pxpm-8jw2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mq5v-pxpm-8jw2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.982Z"},{"id":"sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-41236","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.326Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-676b4fedaf283e5dc41a2ab2206e6e62"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"### Summary\nFroxlor 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.\n\nIf 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.\n\n### Details\nThe 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()`:\n\n```php\n// customer_ftp.php:251-253\nif ($action == 'add' && Request::post('send') == 'send') {\n    $result = $log->logAction(USR_ACTION, LOG_INFO, \"added SSH-key\");\n    Commands::get()->apiCall('SshKeys.add', Request::postAll());\n}\n```\n\nOn the server side, the add handler stores the public key and schedules an NSS rebuild as lon","public_affected_ranges":["= 2.3.6"]},{"certainty":"source_listed","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"### Summary\nFroxlor 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.\n\nIf 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.\n\n### Details\nThe 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()`:\n\n```php\n// customer_ftp.php:251-253\nif ($action == 'add' && Request::post('send') == 'send') {\n    $result = $log->logAction(USR_ACTION, LOG_INFO, \"added SSH-key\");\n    Commands::get()->apiCall('SshKeys.add', Request::postAll());\n}\n```\n\nOn the server side, the add handler stores the public key and schedules an NSS rebuild as lon","public_affected_ranges":["ECOSYSTEM: introduced 2.3.6; fixed 2.3.7"]}],"null_published_at":"2026-11-08T15:11:47.511Z","source_updated_at":"2026-06-09T11:54:23.000Z","source_disclosed_at":"2026-05-29T15:40:23.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.982Z"},{"id":"NVI-00008041","kind":"vulnerability","title":"Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mq5v-pxpm-8jw2","CVE-2026-41236"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.3.7 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.366%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.30649. Missing scores are unknown.","source_id":"sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-f30c0c7d173bf7eda003cb2533bbf948","url":"https://github.com/advisories/GHSA-mq5v-pxpm-8jw2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mq5v-pxpm-8jw2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.982Z"},{"id":"sr-1266e2ae4c4b5eb4f5eb3e062a6ddb80","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-41236","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.326Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"### Summary\nFroxlor 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.\n\nIf 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.\n\n### Details\nThe 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()`:\n\n```php\n// customer_ftp.php:251-253\nif ($action == 'add' && Request::post('send') == 'send') {\n    $result = $log->logAction(USR_ACTION, LOG_INFO, \"added SSH-key\");\n    Commands::get()->apiCall('SshKeys.add', Request::postAll());\n}\n```\n\nOn the server side, the add handler stores the public key and schedules an NSS rebuild as lon","public_affected_ranges":["ECOSYSTEM: introduced 2.3.6; fixed 2.3.7"]}],"null_published_at":"2026-11-08T08:10:32.024Z","source_updated_at":"2026-09-10T03:51:06.498Z","source_disclosed_at":"2026-05-29T15:40:23.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.982Z"},{"id":"NVI-00008041","kind":"vulnerability","title":"Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mq5v-pxpm-8jw2","CVE-2026-41236"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.3.7 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-86ac208d6875838ecf35e8a0ac6612fe"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.366%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.30502. Missing scores are unknown.","source_id":"sr-86ac208d6875838ecf35e8a0ac6612fe"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-f30c0c7d173bf7eda003cb2533bbf948","url":"https://github.com/advisories/GHSA-mq5v-pxpm-8jw2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mq5v-pxpm-8jw2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.982Z"},{"id":"sr-86ac208d6875838ecf35e8a0ac6612fe","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-41236","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.378Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"### Summary\nFroxlor 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.\n\nIf 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.\n\n### Details\nThe 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()`:\n\n```php\n// customer_ftp.php:251-253\nif ($action == 'add' && Request::post('send') == 'send') {\n    $result = $log->logAction(USR_ACTION, LOG_INFO, \"added SSH-key\");\n    Commands::get()->apiCall('SshKeys.add', Request::postAll());\n}\n```\n\nOn the server side, the add handler stores the public key and schedules an NSS rebuild as lon","public_affected_ranges":["ECOSYSTEM: introduced 2.3.6; fixed 2.3.7"]}],"null_published_at":"2026-11-03T02:33:09.115Z","source_updated_at":"2026-09-10T03:51:06.498Z","source_disclosed_at":"2026-05-29T15:40:23.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.982Z"},{"id":"NVI-00008041","kind":"vulnerability","title":"Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mq5v-pxpm-8jw2","CVE-2026-41236"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.3.7 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-f30c0c7d173bf7eda003cb2533bbf948","url":"https://github.com/advisories/GHSA-mq5v-pxpm-8jw2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mq5v-pxpm-8jw2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.982Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f30c0c7d173bf7eda003cb2533bbf948"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"### Summary\nFroxlor 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.\n\nIf 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.\n\n### Details\nThe 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()`:\n\n```php\n// customer_ftp.php:251-253\nif ($action == 'add' && Request::post('send') == 'send') {\n    $result = $log->logAction(USR_ACTION, LOG_INFO, \"added SSH-key\");\n    Commands::get()->apiCall('SshKeys.add', Request::postAll());\n}\n```\n\nOn the server side, the add handler stores the public key and schedules an NSS rebuild as lon","public_affected_ranges":["ECOSYSTEM: introduced 2.3.6; fixed 2.3.7"]}],"null_published_at":"2026-10-31T22:13:22.827Z","source_updated_at":"2026-09-10T03:51:06.498Z","source_disclosed_at":"2026-05-29T15:40:23.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.982Z"}],"next_cursor":null,"snapshot_revision":"42594"}