CVE-2025-10282: BLSOPS bbot · Information Exposure
Affects BLSOPS bbotSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BLSOPS, LLC bbot | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should implement strict validation and sanitization of all git URLs processed by the bbot gitlab module to prevent malicious formatting. Limit the scope and permissions of GitLab API keys to the minimum necessary, employing the principle of least privilege. Rotate API keys regularly and monitor their usage for suspicious activity. Educate users about the risks of interacting with untrusted git URLs, especially in automated workflows. Employ network controls to restrict outbound connections from bbot to only trusted destinations, reducing the risk of data exfiltration. If possible, update or patch the bbot product once a fix is released by BLSOPS, LLC. Additionally, implement logging and alerting on API key usage anomalies to detect potential exploitation attempts early. Consider isolating the bbot environment to limit the blast radius of any compromise.
Description
BBOT's gitlab module could be abused to disclose a GitLab API key to an attacker controlled server with a malicious formatted git URL.