Is CVE-2026-93853 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-93853 being exploited in the wild.

How severe is CVE-2026-93853?

Informational severity, published 29 September 2026.

Which products and versions are affected?

EnterpriseDB Barman 3.4.0 to 3.20.0 (AWS from 3.7.0, Azure from 3.6.0, Google Cloud from 3.4.0).

Is there a fix for CVE-2026-93853?

A patch was published on 2026-09-29: Fixed in Barman 3.20.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-93853 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-93853?

Check whether you run EnterpriseDB Barman at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-93853: Barman snapshot backup deletion privilege escalation

CVE-2026-93853 · Severity: info · Published 2026-09-29

Barman is a backup and recovery tool for PostgreSQL that manages cloud snapshots. An attacker who can modify Barman's backup catalog file can trick Barman into deleting arbitrary cloud snapshots using Barman's own credentials, potentially destroying critical backups or data. This requires the attacker to have write access to the backup catalog but not direct snapshot deletion permissions, exploiting a mismatch in how different users access these systems.

Vendors: EnterpriseDB.

Quick answers

Is CVE-2026-93853 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-93853 being exploited in the wild.
How severe is CVE-2026-93853?: Informational severity, published 29 September 2026.
Which products and versions are affected?: EnterpriseDB Barman 3.4.0 to 3.20.0 (AWS from 3.7.0, Azure from 3.6.0, Google Cloud from 3.4.0).
Is there a fix for CVE-2026-93853?: A patch was published on 2026-09-29: Fixed in Barman 3.20.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-93853 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-93853?: Check whether you run EnterpriseDB Barman at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an unverified ownership flaw in snapshot deletion logic. When Barman deletes a snapshot backup, it reads snapshot identifiers from backup.info without verifying that the snapshots actually belong to that backup before passing them to the cloud provider API. An attacker with write access to backup.info can substitute arbitrary snapshot IDs, causing Barman to delete any snapshot its cloud identity can reach on AWS, Azure, or GCP. This requires a split-identity deployment where the catalog writer differs from the Barman cloud deletion identity.

Affected products

EnterpriseDB Barman 3.4.0 to 3.20.0 (AWS from 3.7.0, Azure from 3.6.0, Google Cloud from 3.4.0)

Timeline

2026-09-29: disclosed
2026-09-29: patched: Fixed in Barman 3.20.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.