PoC Monitor
← All CVEs
CVE-2026-93853published 29 Sep 2026 20:55 UTCData: JSON · API

EnterpriseDB Barman

Barman snapshot backup deletion trusts unverified backup catalog metadata

Unverified ownership in Barman snapshot backup deletion allows a principal who can write the backup catalog to cause Barman to delete unrelated cloud snapshots. When a snapshot backup is deleted, either explicitly or by retention policy enforcement, Barman reads the snapshot identifiers from the backup.info file and passes them to the cloud provider's delete API using Barman's own credentials, without verifying that the snapshots belong to that backup. An attacker who can overwrite backup.info but lacks snapshot delete permissions can substitute the identifiers of other snapshots, causing Barman to delete any snapshot its cloud identity can reach on AWS, Microsoft Azure, or Google Cloud. Exploitation requires a deployment where the principal that writes the backup catalog is separate from the identity Barman uses to delete snapshots. Barman versions from 3.4.0 (Google Cloud), 3.6.0 (Azure), and 3.7.0 (AWS) up to and including 3.20.0 are affected. The issue is fixed in Barman 3.20.1.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.2high · scored by CNA · CWE-283
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

EnterpriseDB Barman
  • >= 3.4.0, < 3.20.1

Fixed in 3.20.1

Mitigation

Upgrade to Barman 3.20.1 or later. Before deleting a snapshot, Barman now reads the snapshot name from the cloud provider and refuses the deletion unless it matches the backup being deleted.

Workaround

Restrict write access to the backup catalog in object storage to the identity Barman uses. Enable object versioning or object lock on the backup bucket, and on AWS use EBS Snapshot Lock (aws_snapshot_lock_mode) to protect snapshots from deletion.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published29 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.