Cloud snapshot deletion via unverified backup metadata
Published Sep 29, 2026 · Updated Sep 29, 2026
Snapshot deletion in EnterpriseDB Barman 3.4.0 through 3.20.0 allows attackers with catalog write access to delete unrelated cloud snapshots. During backup deletion or retention cleanup, Barman reads snapshot IDs from backup.info and sends them to the cloud delete API without checking backup ownership. Exploitation requires separate catalog-write and cloud-delete identities; substituted IDs can target snapshots reachable by Barman's cloud credentials.
Summary
What happened
Snapshot deletion in EnterpriseDB Barman 3.4.0 through 3.20.0 allows attackers with catalog write access to delete unrelated cloud snapshots. During backup deletion or retention cleanup, Barman reads snapshot IDs from backup.info and sends them to the cloud delete API without checking backup ownership. Exploitation requires separate catalog-write and cloud-delete identities; substituted IDs can target snapshots reachable by Barman's cloud credentials.
The record
- CVE
- CVE-2026-93853
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- EnterpriseDB
- Product
- Barman
- Classifications
- T1485
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.4.0 <3.20.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started