Skip to main content
VulnerabilityPublished

CVE-2025-10283: BLSOPS bbot · Path Traversal

Affects BLSOPS bbotSource CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
BLSOPS, LLC bbotAffected
  • =0.0.0
Fixed in–

AI-suggested

  1. Immediately restrict or disable the gitdumper module in bbot until a vendor patch is available.
  2. Implement strict validation and sanitization of all git repository inputs to prevent processing of malicious repositories.
  3. Employ network segmentation and firewall rules to limit access to systems running bbot, especially restricting inbound connections to trusted sources.
  4. Monitor logs and network traffic for unusual git activity or unexpected command executions related to bbot.
  5. Use application whitelisting and endpoint detection and response (EDR) solutions to detect and block unauthorized command execution.
  6. Engage with BLSOPS, LLC for timely updates and patches and apply them as soon as they are released.
  7. Conduct security awareness training for users who interact with bbot to recognize and avoid triggering malicious repositories.
  8. Consider deploying runtime application self-protection (RASP) mechanisms to detect and prevent exploitation attempts in real-time.
  9. Review and harden permissions on directories and files accessed by bbot to minimize the impact of path traversal.
  10. Prepare incident response plans specific to potential exploitation scenarios involving bbot.

Description

BBOT's gitdumper module could be abused to execute commands through a malicious git repository.

References

Community reviews

Loading reviews…