Victim-record corruption via non-atomic registration
Published Sep 4, 2026 · Updated Sep 4, 2026
Race condition in Jofpin Trape 2.0 Telemetry Endpoint allows remote attackers to corrupt victim records via concurrent registrations. The /register route reads attacker-controlled vId, checks for an existing record, then performs separate unprotected SQL inserts without a transaction or consistent uniqueness constraints. No authentication is required, but successful timing requires concurrent requests; exploitation duplicates analytics rows and triggers an unhandled database error.
Summary
What happened
Race condition in Jofpin Trape 2.0 Telemetry Endpoint allows remote attackers to corrupt victim records via concurrent registrations. The /register route reads attacker-controlled vId, checks for an existing record, then performs separate unprotected SQL inserts without a transaction or consistent uniqueness constraints. No authentication is required, but successful timing requires concurrent requests; exploitation duplicates analytics rows and triggers an unhandled database error.
The record
- CVE
- CVE-2026-85639
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- Jofpin
- Product
- Trape
- Classifications
- CWE-362, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=2.0
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
- Concurrent duplicate-registration proof of conceptproof of concept · unverified
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