CVE-2025-44043: Keyoti SearchUnit · Server-Side Request Forgery (SSRF)
Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 9.0.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade keyoti.searchunit to 9.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetkeyoti.searchunitpkg:nuget/keyoti.searchunitOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade Keyoti SearchUnit to version 9.0.0 or later where this vulnerability is addressed.
- If immediate upgrade is not feasible, implement network-level controls to restrict outbound SMB traffic from the SearchUnit server to untrusted networks or hosts.
- Employ web application firewalls (WAFs) to detect and block suspicious POST requests targeting the vulnerable endpoints, especially those containing SMB paths in the indexDirectory parameter.
- Conduct thorough logging and monitoring of SearchUnit server network activity, focusing on unusual SMB connections or configuration file changes.
- Restrict permissions on configuration and log files to minimize the impact of unauthorized read/write operations.
- Educate users about the risks of interacting with untrusted content that might trigger SSRF attacks requiring user interaction.
- Regularly audit and review SearchUnit server configurations and access controls to detect anomalies.
- Consider network segmentation to isolate SearchUnit servers from sensitive internal resources and SMB shares.
Description
Keyoti SearchUnit prior to 9.0.0.is vulnerable to Server-Side Request Forgery (SSRF) in /Keyoti_SearchEngine_Web_Common/SearchService.svc/GetResults and /Keyoti_SearchEngine_Web_Common/SearchService.svc/GetLocationAndContentCategories. An attacker can specify their own SMB server as the indexDirectory value when making POST requests to the affected components. In doing so an attacker can get the SearchUnit server to read and write configuration and log files from/to the attackers server.