Database/Control plane, storage & DevOps
Pure Storage FlashBlade object store protocol: An authenticated object-store user degrades both data access and
Impact
An authenticated object-store user degrades both data access and replication for the whole array. One tenant's S3 client can therefore interrupt everyone else's reads and break the copy that was supposed to be the recovery point.
Who can reach it
Any authenticated client of the FlashBlade object store protocol - the same access a tenant needs to use their own bucket.
What to do
Upgrade Purity//FB to the fixed release named in Pure's bulletin. Monitor replication lag as a signal while unpatched, since the replication impact is the part that quietly breaks recovery.
References
Related entries
- OpenVINO Model Server: Input-validation flaw in OpenVINO Model Server reachable without authenticationCVE-2023-31203 · OpenVINO Model ServerMedium
- GitLab: crafted Git ref names make the web UI show different content than the downloaded archiveCVE-2025-12506 · GitLab CE/EE (Git reference name resolution)Medium
- Terraform Enterprise: users without write access can create state versions and steer later appliesCVE-2025-13432 · HashiCorp Terraform Enterprise (workspace state version permissions)Medium
- Kibana: Open redirect leading to SSRF via a specially crafted URLCVE-2025-25012 · KibanaMedium
- GitLab CE/EE: authenticated user can create issues with locked discussions without the required permissionCVE-2026-102907 · GitLab CE/EE (issue discussion locking)Medium
- GitLab EE: custom role with compliance framework admin can run crafted pipelines across group projectsCVE-2026-104661 · GitLab EE (compliance framework administration, compliance pipeline execution)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.