CVE-2026-93853 (GCVE-0-2026-93853)
Vulnerability from cvelistv5
Published
2026-09-29 20:55
Modified
2026-09-30 15:28
CWE
Summary
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.
Impacted products
Vendor Product Version
EnterpriseDB Barman Version: 3.4.0   < 3.20.1
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-93853",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-30T15:04:52.773679Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-30T15:28:16.037Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://github.com/EnterpriseDB/barman",
          "defaultStatus": "unaffected",
          "product": "Barman",
          "vendor": "EnterpriseDB",
          "versions": [
            {
              "lessThan": "3.20.1",
              "status": "affected",
              "version": "3.4.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Mufeed VH of Winfunc"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s delete API using Barman\u0027s 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."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "baseScore": 7.2,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H",
            "version": "4.0"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-283",
              "description": "CWE-283 Unverified Ownership",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-29T20:55:51.959Z",
        "orgId": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
        "shortName": "EDB"
      },
      "references": [
        {
          "url": "https://www.enterprisedb.com/docs/security/advisories/cve202693853/"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Barman snapshot backup deletion trusts unverified backup catalog metadata",
      "workarounds": [
        {
          "lang": "en",
          "value": "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."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
    "assignerShortName": "EDB",
    "cveId": "CVE-2026-93853",
    "datePublished": "2026-09-29T20:55:51.959Z",
    "dateReserved": "2026-09-18T18:52:15.463Z",
    "dateUpdated": "2026-09-30T15:28:16.037Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"cna\": {\"title\": \"Barman snapshot backup deletion trusts unverified backup catalog metadata\", \"source\": {\"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Mufeed VH of Winfunc\"}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"version\": \"4.0\", \"baseScore\": 7.2, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H\"}}], \"affected\": [{\"vendor\": \"EnterpriseDB\", \"product\": \"Barman\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.4.0\", \"lessThan\": \"3.20.1\", \"versionType\": \"custom\"}], \"collectionURL\": \"https://github.com/EnterpriseDB/barman\", \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"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.\"}], \"references\": [{\"url\": \"https://www.enterprisedb.com/docs/security/advisories/cve202693853/\"}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"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.\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\u0027s delete API using Barman\u0027s 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.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-283\", \"description\": \"CWE-283 Unverified Ownership\"}]}], \"providerMetadata\": {\"orgId\": \"20be33e2-bf35-4d13-8fad-18bd2f3e3659\", \"shortName\": \"EDB\", \"dateUpdated\": \"2026-09-29T20:55:51.959Z\"}}, \"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-93853\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-09-30T15:04:52.773679Z\"}}}], \"providerMetadata\": {\"shortName\": \"CISA-ADP\", \"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"dateUpdated\": \"2026-09-30T15:26:07.297Z\"}}]}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-93853\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-09-29T20:55:51.959Z\", \"dateReserved\": \"2026-09-18T18:52:15.463Z\", \"assignerOrgId\": \"20be33e2-bf35-4d13-8fad-18bd2f3e3659\", \"datePublished\": \"2026-09-29T20:55:51.959Z\", \"assignerShortName\": \"EDB\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…