CVE-2025-10283 json
Improper .git Sanitization in gitdumper Enables RCE
published last yr. modified 15d ago also GHSA-h6m2-r6h9-4c44 , PYSEC-2026-293 , EUVD-2025-33394
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
BBOT's gitdumper module could be abused to execute commands through a malicious git repository.
Patch / fix
Is CVE-2025-10283 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | bbot | <2.7.0 |
2.7.0 |
Affected products
- BLSOPS, LLC bbot
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/blacklanternsecurity/bbot/commit/0ede97fa887de33fcfd1378b4213a09c21dc6140
web
-
blog.blacklanternsecurity.com
/p/bbot-security-advisory-gitdumper
web
-
github.com
/blacklanternsecurity/bbot/security/advisories/GHSA-h6m2-r6h9-4c44
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-10283
advisory
-
github.com
/blacklanternsecurity/bbot
package
-
github.com
/pypa/advisory-database/tree/main/vulns/bbot/PYSEC-2026-293.yaml
web
-
pypi.org
/project/bbot
web, package
-
github.com
/advisories/GHSA-h6m2-r6h9-4c44
advisory
Sources
- CVE List CVE-2025-10283
- GitHub Advisory GHSA-h6m2-r6h9-4c44
- NVD CVE-2025-10283
- OSV PYSEC-2026-293
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.