# CVE-2026-14687: 666ghj BettaFish InsightEngine search-result Deduplication agent.py _deduplicate_results partial string comparison

> Attackers can manipulate search result deduplication via partial string comparison flaws in the InsightEngine agent, potentially bypassing logic checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-v6hv-2p8r-43v4

## What is CVE-2026-14687?

CVE-2026-14687 is a medium-severity vulnerability in 666ghj BettaFish, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in 666ghj BettaFish up to 1.2.1. Impacted is the function _deduplicate_results of the file InsightEngine/agent.py of the component InsightEngine search-result Deduplication. Executing a manipulation can lead to partial string comparison. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.

Weakness: CWE-697 (Incorrect Comparison), CWE-187 (Partial String Comparison)

## Which versions are affected by CVE-2026-14687?


## How do I fix CVE-2026-14687?

No fix has been published for CVE-2026-14687 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14687 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14687 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14687 and fix it if it is affected.

What it is: CVE-2026-14687 is a medium-severity vulnerability in 666ghj BettaFish, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14687 exists.

Affected product: 666ghj BettaFish. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14687/ (Markdown: https://insights.sbomify.com/CVE-2026-14687/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14687
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14687
- OSV: https://osv.dev/vulnerability/CVE-2026-14687

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14687/
Summaries are generated and may contain mistakes; the official description above is the record.