Result suppression via truncated deduplication key
Published Jul 5, 2026 · Updated Jul 5, 2026
Incorrect comparison in 666ghj BettaFish 1.2.0 through 1.2.1 allows remote attackers to suppress distinct InsightEngine results. The _deduplicate_results function uses only the first 100 characters of URL-less content as its fallback identity, so a later record with the same prefix is discarded. Exploitation requires attacker-controlled content to enter a URL-less result path and can make generated analysis incomplete or misleading without reading host data or interrupting service.
Summary
What happened
Incorrect comparison in 666ghj BettaFish 1.2.0 through 1.2.1 allows remote attackers to suppress distinct InsightEngine results. The _deduplicate_results function uses only the first 100 characters of URL-less content as its fallback identity, so a later record with the same prefix is discarded. Exploitation requires attacker-controlled content to enter a URL-less result path and can make generated analysis incomplete or misleading without reading host data or interrupting service.
The record
- CVE
- CVE-2026-14687
- Published
- Jul 5, 2026
- Updated
- Jul 5, 2026
- Vendor
- 666ghj
- Product
- BettaFish
- Classifications
- CWE-187, CWE-697, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2026CVE publishedPublication date reported by the CVE source.
- Jul 5, 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=1.2.0
- Affected versionversion=1.2.1
What conditions does exploitation require?
What is affected?
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
- GitHub issue #688 minimal reproductionproof of concept · demonstrated
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