« Volver al listado

CVE-2026-40683

Estado: Pendiente de análisisAlta (7.7)—

In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boolean when the user_enabled_invert configuration option is False (the default). The _ldap_res_to_model method in the UserApi class only performed string-to-boolean conversion when user_enabled_invert was True. When False, the raw string value from LDAP (e.g., "FALSE") was used directly. Since non-empty strings are truthy in Python, users marked as disabled in LDAP were treated as enabled by Keystone, allowing them to authenticate and perform actions. All deployments using the LDAP identity backend without user_enabled_invert=True or user_enabled_emulation are affected.

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Explotación remota de Keystone LDAP por falta de conversión de booleanos (AV:N, PR:L) permitiendo autenticación de usuarios deshabilitados. Impacto: bypass de autenticación (T1078.001) y potencial ejecución de acciones (T1059).

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Privileged Account ManagementDisable or Remove Feature or ProgramVulnerability ScanningThreat Intelligence ProgramRestrict Web-Based ContentPassword Policies

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Openstack — KeystoneAI

CWE

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2026-40683",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-40683",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-04-14T20:14:37.459439Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "cve@mitre.org",
        "cvssData": {
          "scope": "CHANGED",
          "version": "3.1",
          "baseScore": 7.7,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H",
          "integrityImpact": "LOW",
          "userInteraction": "NONE",
          "attackComplexity": "HIGH",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "LOW"
        },
        "impactScore": 5.3,
        "exploitabilityScore": 1.8
      }
    ]
  },
  "affected": [
    {
      "source": "cve@mitre.org",
      "affectedData": [
        {
          "vendor": "OpenStack",
          "product": "Keystone",
          "versions": [
            {
              "status": "affected",
              "version": "8.0.0",
              "lessThan": "25.0.1",
              "versionType": "semver"
            },
            {
              "status": "affected",
              "version": "26.0.0",
              "lessThan": "26.1.1",
              "versionType": "semver"
            },
            {
              "status": "affected",
              "version": "27.0.0",
              "lessThan": "27.0.1",
              "versionType": "semver"
            },
            {
              "status": "affected",
              "version": "28.0.0",
              "lessThan": "28.0.1",
              "versionType": "semver"
            }
          ],
          "defaultStatus": "unaffected"
        }
      ]
    }
  ],
  "published": "2026-04-14T20:16:48.203",
  "references": [
    {
      "url": "https://bugs.launchpad.net/keystone/+bug/2121152",
      "source": "cve@mitre.org"
    },
    {
      "url": "https://bugs.launchpad.net/keystone/+bug/2141713",
      "source": "cve@mitre.org"
    },
    {
      "url": "https://review.opendev.org/958205",
      "source": "cve@mitre.org"
    },
    {
      "url": "https://www.openwall.com/lists/oss-security/2026/04/14/9",
      "source": "cve@mitre.org"
    },
    {
      "url": "http://www.openwall.com/lists/oss-security/2026/08/05/17",
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "cve@mitre.org",
      "description": [
        {
          "lang": "en",
          "value": "CWE-843"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boolean when the user_enabled_invert configuration option is False (the default). The _ldap_res_to_model method in the UserApi class only performed string-to-boolean conversion when user_enabled_invert was True. When False, the raw string value from LDAP (e.g., \"FALSE\") was used directly. Since non-empty strings are truthy in Python, users marked as disabled in LDAP were treated as enabled by Keystone, allowing them to authenticate and perform actions. All deployments using the LDAP identity backend without user_enabled_invert=True or user_enabled_emulation are affected."
    },
    {
      "lang": "es",
      "value": "En OpenStack Keystone anterior a 28.0.1, el backend de identidad LDAP no convierte el atributo enabled del usuario a un booleano cuando la opción de configuración user_enabled_invert es False (el valor predeterminado). El método _ldap_res_to_model en la clase UserApi solo realizaba la conversión de cadena a booleano cuando user_enabled_invert era True. Cuando era False, el valor de cadena sin procesar de LDAP (por ejemplo, 'FALSE') se usaba directamente. Dado que las cadenas no vacías son truthy en Python, los usuarios marcados como deshabilitados en LDAP eran tratados como habilitados por Keystone, permitiéndoles autenticarse y realizar acciones. Todas las implementaciones que utilizan el backend de identidad LDAP sin user_enabled_invert=True o user_enabled_emulation se ven afectadas."
    }
  ],
  "lastModified": "2026-08-05T19:17:29.843",
  "sourceIdentifier": "cve@mitre.org"
}