MongoDBGHSA-x24p-wj69-446q
RUBY-3941 Require exact match when reading/writing GridFS via ID
Medium6.1CVE-2026-88030 · Published Sep 15, 2026
### Impact When reading/writing via an ID with the GridFS API, require an exact match on the given ID. Otherwise, if a Hash is given in place of the ID, it may be interpreted as criteria, overriding the ID match. ### Patches Patch available in mongo >= 2.26.0 ### Workarounds Ensure your existing workflow _only_ supports exact matching on the GridFS API. ### References [RUBY-3941](https://jira.mongodb.org/browse/RUBY-3941)
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| mongo RubyGems | < 2.26.0 | 2.26.0 |
Details and references
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-943
More MongoDB advisories
All MongoDB| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Sep 17 | Insertion of Sensitive Information into Log File | Medium5.7 | 8.4.4 |
| Sep 17 | Silent plaintext storage of encrypted fields via mis-keyed encryption map in the EF Core provider | Medium6.8 | 8.4.4 |
| Sep 17 | MongoDB C Driver: integer overflow | Medium6.9 | 2.3.1 |
| Sep 17 | A flaw in libmongoc's SCRAM authentication implementation caused the client to... | Medium6.3 | 2.3.2 |
| Sep 17 | MongoDB Entity Framework Core Provider: missing encryption | Medium6.8 | 8.4.3+2 more |
| Sep 15 | PYTHON-5994 Use exact match for file ID in GridFS delete methods | Medium6.1 | 4.18.1 |