Unauthenticated write-protection removal via failed setup authentication
Published Aug 21, 2026 · Updated Aug 21, 2026
Missing authentication in Combodo iTop before 3.2.3 allows remote attackers to delete the .readonly setup-control file. The setup authentication failure path still runs its cleanup phase, which removes .readonly instead of preserving it after rejecting the request. No account or user interaction is required; deleting the file removes the control that blocks write actions, weakening integrity and availability protections.
Summary
What happened
Missing authentication in Combodo iTop before 3.2.3 allows remote attackers to delete the .readonly setup-control file. The setup authentication failure path still runs its cleanup phase, which removes .readonly instead of preserving it after rejecting the request. No account or user interaction is required; deleting the file removes the control that blocks write actions, weakening integrity and availability protections.
The record
- CVE
- CVE-2026-34949
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- Combodo
- Product
- iTop
- Classifications
- CWE-306, CAPEC-166, T1562
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=< 3.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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