Local code execution via unsafe .totp import
Published Aug 3, 2026 · Updated Aug 3, 2026
Object injection in TÜBİTAK BİLGEM eta-otp-lock before 1.0.4 allows local users to execute code through a crafted .totp file. The .totp import handler passed the selected file to Python pickle deserialization without restricting which globals could be resolved. Opening a crafted .totp file requires user interaction and can execute attacker-selected code with the application's privileges.
Summary
What happened
Object injection in TÜBİTAK BİLGEM eta-otp-lock before 1.0.4 allows local users to execute code through a crafted .totp file. The .totp import handler passed the selected file to Python pickle deserialization without restricting which globals could be resolved. Opening a crafted .totp file requires user interaction and can execute attacker-selected code with the application's privileges.
The record
- CVE
- CVE-2026-18642
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- TÜBİTAK BİLGEM Software Technologies Research Institute
- Product
- eta-otp-lock
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <1.0.4
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