Persistent SSH access via authorized_keys line injection
Published Sep 13, 2026 · Updated Sep 13, 2026
SSH key injection in Froxlor before 2.3.12 allows remote authenticated users to gain persistent unauthorized SSH access. The SshKeys::add() endpoint accepts embedded newlines, causing attacker-controlled option directives and key entries to become separate authorized_keys lines. Customer access with shell capability and permission to add a key is required; injected entries remain effective after key deletion or SSH access revocation.
Summary
What happened
SSH key injection in Froxlor before 2.3.12 allows remote authenticated users to gain persistent unauthorized SSH access. The SshKeys::add() endpoint accepts embedded newlines, causing attacker-controlled option directives and key entries to become separate authorized_keys lines. Customer access with shell capability and permission to add a key is required; injected entries remain effective after key deletion or SSH access revocation.
The record
- CVE
- CVE-2026-90767
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- T1098.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2026CVE publishedPublication date reported by the CVE source.
- Sep 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo