---
title: Vault PKI ACME default directory uses sign-verbatim-unsafe
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > Code Security > Infrastructure as Code (IaC)
  Security > IaC Security Rules > Vault PKI ACME default directory uses
  sign-verbatim-unsafe
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Vault PKI ACME default directory uses sign-verbatim-unsafe

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

## Metadata{% #metadata %}

**Id:** `terraform-vault-pki-acme-sign-verbatim-unsafe-default-directory-policy` 

**Platform:** Terraform

**Severity:** Medium

**Category:** Insecure Defaults

#### Learn More{% #learn-more %}

- [Provider Reference](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/pki_secret_backend_config_acme)

### Description{% #description %}

The `vault_pki_secret_backend_config_acme` resource enables Vault's PKI secrets engine ACME server with `default_directory_policy` set to `sign-verbatim-unsafe`. This value explicitly opts in to the behavior fixed by HCSEC-2026-40 / CVE-2026-105818: Vault copies subject alternative name types that the ACME protocol never validates (anything other than DNS names and IP addresses, such as email addresses, URIs, or other names) from the certificate signing request into the issued certificate. An ACME client that completes validation for an identifier it controls can therefore obtain a certificate that also asserts other, unverified identities, enabling impersonation toward systems that trust the Vault PKI mount. To remediate, set `default_directory_policy` to `sign-verbatim`, which rejects these requests on fixed Vault versions, or to `forbid` or a `role:<role>` whose constraints exclude unverified subject alternative name types.

## Compliant Code Examples{% #compliant-code-examples %}

```terraform
resource "vault_pki_secret_backend_config_acme" "negative1" {
  backend                  = vault_mount.pki.path
  enabled                  = true
  default_directory_policy = "forbid"
}
```

```terraform
resource "vault_pki_secret_backend_config_acme" "negative2" {
  backend                  = vault_mount.pki.path
  enabled                  = true
  default_directory_policy = "role:acme-restricted"
  allowed_roles            = ["acme-restricted"]
}
```

```terraform
resource "vault_pki_secret_backend_config_acme" "negative3" {
  backend = vault_mount.pki.path
  enabled = false
}
```

## Non-Compliant Code Examples{% #non-compliant-code-examples %}

```terraform
resource "vault_pki_secret_backend_config_acme" "positive1" {
  backend                  = vault_mount.pki.path
  enabled                  = true
  default_directory_policy = "sign-verbatim-unsafe"
}
```
