CVE-2026-42769 (GCVE-0-2026-42769)

Vulnerability from cvelistv5 – Published: 2026-06-09 16:03 – Updated: 2026-06-10 07:48
VLAI
Title
Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate
Summary
Issue Summary: An error in the callback used to verify the certificate provided in a Root CA key update Certificate Management Protocol (CMP) message response rendered the certificate validation ineffectual, which could lead to escalation of credentials from the Registration Authority (RA) level to the root Certification Authority (root CA) level. Impact Summary: The Registration Autority could replace the root CA certificate for the CMP clients with an arbitrary root CA certificate. One of the parts of the Certificate Management Protocol (CMP), specified in RFC 9810, is Root Certification Authority (root CA) key Rollover, which is sent by the server in a message with type 'id-it-rootCaKeyUpdate'. As part of these messages, 'newWithOld' certificate, the new root CA certificate signed with the old root CA key, is provided, and verifying its signature is crucial for transferring the trust from the old CA key to the new one. The 'id-it-rootCaKeyUpdate' messages are expected to be processed with OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the 'newWithOld' certificate. A typo in the certificate chain building code led to adding an incorrect certificate ('newWithOld' instead of 'oldRoot') to the certificate chain, rendering the certificate verification process ineffectual (only the issuer name and the algorithm OIDs were verified by other parts of the verification code). An attacker who already has credentials that satisfy the CMP message protection checks can generate a new key pair and use a crafted self-signed certificate in its 'id-it-rootCaKeyUpdate' CMP messages which affected CMP clients would accept as a new trust anchor. Significant preconditions for the attack (having valid RA-level credentials) are the reason the issue was assigned Low severity. The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
  • CWE-295 - Improper Certificate Validation
Assigner
References
Impacted products
Vendor Product Version
OpenSSL OpenSSL Affected: 4.0.0 , < 4.0.1 (semver)
Affected: 3.6.0 , < 3.6.3 (semver)
Affected: 3.5.0 , < 3.5.7 (semver)
Affected: 3.4.0 , < 3.4.6 (semver)
Create a notification for this product.
Date Public
2026-06-09 14:00
Credits
Alex Gaynor (Anthropic) Alex Gaynor (Anthropic) Bob Beck
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2026-42769",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-06-09T19:38:00.495097Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-06-09T19:38:05.632Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "OpenSSL",
          "vendor": "OpenSSL",
          "versions": [
            {
              "lessThan": "4.0.1",
              "status": "affected",
              "version": "4.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.6.3",
              "status": "affected",
              "version": "3.6.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.5.7",
              "status": "affected",
              "version": "3.5.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.4.6",
              "status": "affected",
              "version": "3.4.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Alex Gaynor (Anthropic)"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Alex Gaynor (Anthropic)"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Bob Beck"
        }
      ],
      "datePublic": "2026-06-09T14:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Issue Summary: An error in the callback used to verify the certificate\u003cbr\u003eprovided in a Root CA key update Certificate Management Protocol (CMP)\u003cbr\u003emessage response rendered the certificate validation ineffectual, which\u003cbr\u003ecould lead to escalation of credentials from the Registration Authority (RA)\u003cbr\u003elevel to the root Certification Authority (root CA) level.\u003cbr\u003e\u003cbr\u003eImpact Summary: The Registration Autority could replace the root CA\u003cbr\u003ecertificate for the CMP clients with an arbitrary root CA certificate.\u003cbr\u003e\u003cbr\u003eOne of the parts of the Certificate Management Protocol (CMP), specified in\u003cbr\u003eRFC 9810, is Root Certification Authority (root CA) key Rollover,\u003cbr\u003ewhich is sent by the server in a message with type \u0027id-it-rootCaKeyUpdate\u0027.\u003cbr\u003eAs part of these messages, \u0027newWithOld\u0027 certificate, the new root CA\u003cbr\u003ecertificate signed with the old root CA key, is provided, and verifying its\u003cbr\u003esignature is crucial for transferring the trust from the old CA key to the\u003cbr\u003enew one.\u003cbr\u003e\u003cbr\u003eThe \u0027id-it-rootCaKeyUpdate\u0027 messages are expected to be processed with\u003cbr\u003eOSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the \u0027newWithOld\u0027\u003cbr\u003ecertificate.  A typo in the certificate chain building code led to adding\u003cbr\u003ean incorrect certificate (\u0027newWithOld\u0027 instead of \u0027oldRoot\u0027) to the\u003cbr\u003ecertificate chain, rendering the certificate verification process ineffectual\u003cbr\u003e(only the issuer name and the algorithm OIDs were verified by other parts\u003cbr\u003eof the verification code).\u003cbr\u003e\u003cbr\u003eAn attacker who already has credentials that satisfy the CMP message\u003cbr\u003eprotection checks can generate a new key pair and use a crafted self-signed\u003cbr\u003ecertificate in its \u0027id-it-rootCaKeyUpdate\u0027 CMP messages which affected CMP\u003cbr\u003eclients would accept as a new trust anchor.\u003cbr\u003e\u003cbr\u003eSignificant preconditions for the attack (having valid RA-level credentials)\u003cbr\u003eare the reason the issue was assigned Low severity.\u003cbr\u003e\u003cbr\u003eThe FIPS modules are not affected by this issue, as the affected code is\u003cbr\u003eoutside the OpenSSL FIPS module boundary."
            }
          ],
          "value": "Issue Summary: An error in the callback used to verify the certificate\nprovided in a Root CA key update Certificate Management Protocol (CMP)\nmessage response rendered the certificate validation ineffectual, which\ncould lead to escalation of credentials from the Registration Authority (RA)\nlevel to the root Certification Authority (root CA) level.\n\nImpact Summary: The Registration Autority could replace the root CA\ncertificate for the CMP clients with an arbitrary root CA certificate.\n\nOne of the parts of the Certificate Management Protocol (CMP), specified in\nRFC 9810, is Root Certification Authority (root CA) key Rollover,\nwhich is sent by the server in a message with type \u0027id-it-rootCaKeyUpdate\u0027.\nAs part of these messages, \u0027newWithOld\u0027 certificate, the new root CA\ncertificate signed with the old root CA key, is provided, and verifying its\nsignature is crucial for transferring the trust from the old CA key to the\nnew one.\n\nThe \u0027id-it-rootCaKeyUpdate\u0027 messages are expected to be processed with\nOSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the \u0027newWithOld\u0027\ncertificate.  A typo in the certificate chain building code led to adding\nan incorrect certificate (\u0027newWithOld\u0027 instead of \u0027oldRoot\u0027) to the\ncertificate chain, rendering the certificate verification process ineffectual\n(only the issuer name and the algorithm OIDs were verified by other parts\nof the verification code).\n\nAn attacker who already has credentials that satisfy the CMP message\nprotection checks can generate a new key pair and use a crafted self-signed\ncertificate in its \u0027id-it-rootCaKeyUpdate\u0027 CMP messages which affected CMP\nclients would accept as a new trust anchor.\n\nSignificant preconditions for the attack (having valid RA-level credentials)\nare the reason the issue was assigned Low severity.\n\nThe FIPS modules are not affected by this issue, as the affected code is\noutside the OpenSSL FIPS module boundary."
        }
      ],
      "metrics": [
        {
          "format": "other",
          "other": {
            "content": {
              "text": "Low"
            },
            "type": "https://openssl-library.org/policies/general/security-policy/"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295 Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-06-10T07:48:06.084Z",
        "orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
        "shortName": "openssl"
      },
      "references": [
        {
          "name": "OpenSSL Advisory",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://openssl-library.org/news/secadv/20260609.txt"
        },
        {
          "name": "4.0.1 git commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/openssl/openssl/commit/d531f21c0fe99067a66fc0ff1161ef127f9cd70b"
        },
        {
          "name": "3.6.3 git commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/openssl/openssl/commit/d35cd473a271bf3ce7bf3d32af53217fb83ae92c"
        },
        {
          "name": "3.5.7 git commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/openssl/openssl/commit/54d0989997e5fc26057009a9782c3441ce3842fb"
        },
        {
          "name": "3.4.6 git commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/openssl/openssl/commit/777b363b16fcf2153bb3ded39dc3838713667c44"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
    "assignerShortName": "openssl",
    "cveId": "CVE-2026-42769",
    "datePublished": "2026-06-09T16:03:28.999Z",
    "dateReserved": "2026-04-29T09:22:27.969Z",
    "dateUpdated": "2026-06-10T07:48:06.084Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-42769",
      "date": "2026-07-22",
      "epss": "0.00262",
      "percentile": "0.17845"
    },
    "microsoft_vex": {
      "current_release_date": "2026-07-21T14:40:50.000Z",
      "cve": "CVE-2026-42769",
      "id": "msrc_CVE-2026-42769",
      "initial_release_date": "2026-06-13T01:05:54.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "4",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-42769.json",
      "version": "4"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-42769\",\"sourceIdentifier\":\"openssl-security@openssl.org\",\"published\":\"2026-06-09T17:17:08.377\",\"lastModified\":\"2026-07-23T08:10:00.137\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Issue Summary: An error in the callback used to verify the certificate\\nprovided in a Root CA key update Certificate Management Protocol (CMP)\\nmessage response rendered the certificate validation ineffectual, which\\ncould lead to escalation of credentials from the Registration Authority (RA)\\nlevel to the root Certification Authority (root CA) level.\\n\\nImpact Summary: The Registration Autority could replace the root CA\\ncertificate for the CMP clients with an arbitrary root CA certificate.\\n\\nOne of the parts of the Certificate Management Protocol (CMP), specified in\\nRFC 9810, is Root Certification Authority (root CA) key Rollover,\\nwhich is sent by the server in a message with type \u0027id-it-rootCaKeyUpdate\u0027.\\nAs part of these messages, \u0027newWithOld\u0027 certificate, the new root CA\\ncertificate signed with the old root CA key, is provided, and verifying its\\nsignature is crucial for transferring the trust from the old CA key to the\\nnew one.\\n\\nThe \u0027id-it-rootCaKeyUpdate\u0027 messages are expected to be processed with\\nOSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the \u0027newWithOld\u0027\\ncertificate.  A typo in the certificate chain building code led to adding\\nan incorrect certificate (\u0027newWithOld\u0027 instead of \u0027oldRoot\u0027) to the\\ncertificate chain, rendering the certificate verification process ineffectual\\n(only the issuer name and the algorithm OIDs were verified by other parts\\nof the verification code).\\n\\nAn attacker who already has credentials that satisfy the CMP message\\nprotection checks can generate a new key pair and use a crafted self-signed\\ncertificate in its \u0027id-it-rootCaKeyUpdate\u0027 CMP messages which affected CMP\\nclients would accept as a new trust anchor.\\n\\nSignificant preconditions for the attack (having valid RA-level credentials)\\nare the reason the issue was assigned Low severity.\\n\\nThe FIPS modules are not affected by this issue, as the affected code is\\noutside the OpenSSL FIPS module boundary.\"},{\"lang\":\"es\",\"value\":\"Resumen del Problema: Un error en la funci\u00f3n de devoluci\u00f3n de llamada utilizada para verificar el certificado proporcionado en una respuesta de mensaje del Protocolo de Gesti\u00f3n de Certificados (CMP) de actualizaci\u00f3n de clave de CA ra\u00edz hizo que la validaci\u00f3n del certificado fuera ineficaz, lo que podr\u00eda llevar a la escalada de credenciales del nivel de Autoridad de Registro (RA) al nivel de Autoridad de Certificaci\u00f3n ra\u00edz (CA ra\u00edz).\\n\\nResumen del Impacto: La Autoridad de Registro podr\u00eda reemplazar el certificado de CA ra\u00edz para los clientes CMP con un certificado de CA ra\u00edz arbitrario.\\n\\nUna de las partes del Protocolo de Gesti\u00f3n de Certificados (CMP), especificado en RFC 9810, es la Sustituci\u00f3n de Clave de Autoridad de Certificaci\u00f3n ra\u00edz (CA ra\u00edz), que es enviada por el servidor en un mensaje de tipo \u0027id-it-rootCaKeyUpdate\u0027. Como parte de estos mensajes, se proporciona el certificado \u0027newWithOld\u0027, el nuevo certificado de CA ra\u00edz firmado con la clave de CA ra\u00edz antigua, y verificar su firma es crucial para transferir la confianza de la clave de CA antigua a la nueva.\\n\\nSe espera que los mensajes \u0027id-it-rootCaKeyUpdate\u0027 sean procesados con OSSL_CMP_get1_rootCaKeyUpdate(), que se espera que verifique el certificado \u0027newWithOld\u0027. Un error tipogr\u00e1fico en el c\u00f3digo de construcci\u00f3n de la cadena de certificados llev\u00f3 a a\u00f1adir un certificado incorrecto (\u0027newWithOld\u0027 en lugar de \u0027oldRoot\u0027) a la cadena de certificados, haciendo que el proceso de verificaci\u00f3n del certificado fuera ineficaz (solo el nombre del emisor y los OID del algoritmo fueron verificados por otras partes del c\u00f3digo de verificaci\u00f3n).\\n\\nUn atacante que ya tiene credenciales que satisfacen las comprobaciones de protecci\u00f3n de mensajes CMP puede generar un nuevo par de claves y usar un certificado autofirmado manipulado en sus mensajes CMP \u0027id-it-rootCaKeyUpdate\u0027 que los clientes CMP afectados aceptar\u00edan como un nuevo ancla de confianza.\\n\\nLas precondiciones significativas para el ataque (tener credenciales v\u00e1lidas a nivel de RA) son la raz\u00f3n por la que el problema fue asignado con severidad Baja.\\n\\nLos m\u00f3dulos FIPS no se ven afectados por este problema, ya que el c\u00f3digo afectado est\u00e1 fuera del l\u00edmite del m\u00f3dulo FIPS de OpenSSL.\"}],\"affected\":[{\"source\":\"openssl-security@openssl.org\",\"affectedData\":[{\"vendor\":\"OpenSSL\",\"product\":\"OpenSSL\",\"defaultStatus\":\"unaffected\",\"versions\":[{\"version\":\"4.0.0\",\"lessThan\":\"4.0.1\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.6.0\",\"lessThan\":\"3.6.3\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.5.0\",\"lessThan\":\"3.5.7\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.4.0\",\"lessThan\":\"3.4.6\",\"versionType\":\"semver\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.6,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-06-09T19:38:00.495097Z\",\"id\":\"CVE-2026-42769\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"openssl-security@openssl.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-295\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"3.4.0\",\"versionEndExcluding\":\"3.4.6\",\"matchCriteriaId\":\"BF7E21E7-AEC0-4882-B1F1-2D056B506F22\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"3.5.0\",\"versionEndExcluding\":\"3.5.7\",\"matchCriteriaId\":\"6B6B9930-C549-4D88-9784-AF32CCDDB87A\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"3.6.0\",\"versionEndExcluding\":\"3.6.3\",\"matchCriteriaId\":\"D41B3C45-EC73-4DC8-989D-B2E2792E102F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*\",\"matchCriteriaId\":\"6E881B9A-1A0A-4BC0-8160-20C00561167D\"}]}]}],\"references\":[{\"url\":\"https://github.com/openssl/openssl/commit/54d0989997e5fc26057009a9782c3441ce3842fb\",\"source\":\"openssl-security@openssl.org\",\"tags\":[\"Patch\"]},{\"url\":\"https://github.com/openssl/openssl/commit/777b363b16fcf2153bb3ded39dc3838713667c44\",\"source\":\"openssl-security@openssl.org\",\"tags\":[\"Patch\"]},{\"url\":\"https://github.com/openssl/openssl/commit/d35cd473a271bf3ce7bf3d32af53217fb83ae92c\",\"source\":\"openssl-security@openssl.org\",\"tags\":[\"Patch\"]},{\"url\":\"https://github.com/openssl/openssl/commit/d531f21c0fe99067a66fc0ff1161ef127f9cd70b\",\"source\":\"openssl-security@openssl.org\",\"tags\":[\"Patch\"]},{\"url\":\"https://openssl-library.org/news/secadv/20260609.txt\",\"source\":\"openssl-security@openssl.org\",\"tags\":[\"Vendor Advisory\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-07-01T09:38:21+00:00",
      "cve": "CVE-2026-42769",
      "id": "CVE-2026-42769",
      "initial_release_date": "2026-06-09T00:00:00+00:00",
      "product_status:fixed": "100",
      "product_status:known_affected": "51",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42769.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-15T05:14:17Z",
      "cve": "CVE-2026-42769",
      "id": "CVE-2026-42769",
      "initial_release_date": "2026-06-13T02:19:20Z",
      "product_status:known_affected": "413",
      "product_status:known_not_affected": "440",
      "product_status:recommended": "73",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-42769",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-42769.json",
      "version": "5"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.3, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-42769\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-06-09T19:38:00.495097Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-06-09T19:37:50.572Z\"}}], \"cna\": {\"title\": \"Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"reporter\", \"value\": \"Alex Gaynor (Anthropic)\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"Alex Gaynor (Anthropic)\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"Bob Beck\"}], \"metrics\": [{\"other\": {\"type\": \"https://openssl-library.org/policies/general/security-policy/\", \"content\": {\"text\": \"Low\"}}, \"format\": \"other\"}], \"affected\": [{\"vendor\": \"OpenSSL\", \"product\": \"OpenSSL\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.0.0\", \"lessThan\": \"4.0.1\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"3.6.0\", \"lessThan\": \"3.6.3\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"3.5.0\", \"lessThan\": \"3.5.7\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"3.4.0\", \"lessThan\": \"3.4.6\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unaffected\"}], \"datePublic\": \"2026-06-09T14:00:00.000Z\", \"references\": [{\"url\": \"https://openssl-library.org/news/secadv/20260609.txt\", \"name\": \"OpenSSL Advisory\", \"tags\": [\"vendor-advisory\"]}, {\"url\": \"https://github.com/openssl/openssl/commit/d531f21c0fe99067a66fc0ff1161ef127f9cd70b\", \"name\": \"4.0.1 git commit\", \"tags\": [\"patch\"]}, {\"url\": \"https://github.com/openssl/openssl/commit/d35cd473a271bf3ce7bf3d32af53217fb83ae92c\", \"name\": \"3.6.3 git commit\", \"tags\": [\"patch\"]}, {\"url\": \"https://github.com/openssl/openssl/commit/54d0989997e5fc26057009a9782c3441ce3842fb\", \"name\": \"3.5.7 git commit\", \"tags\": [\"patch\"]}, {\"url\": \"https://github.com/openssl/openssl/commit/777b363b16fcf2153bb3ded39dc3838713667c44\", \"name\": \"3.4.6 git commit\", \"tags\": [\"patch\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Issue Summary: An error in the callback used to verify the certificate\\nprovided in a Root CA key update Certificate Management Protocol (CMP)\\nmessage response rendered the certificate validation ineffectual, which\\ncould lead to escalation of credentials from the Registration Authority (RA)\\nlevel to the root Certification Authority (root CA) level.\\n\\nImpact Summary: The Registration Autority could replace the root CA\\ncertificate for the CMP clients with an arbitrary root CA certificate.\\n\\nOne of the parts of the Certificate Management Protocol (CMP), specified in\\nRFC 9810, is Root Certification Authority (root CA) key Rollover,\\nwhich is sent by the server in a message with type \u0027id-it-rootCaKeyUpdate\u0027.\\nAs part of these messages, \u0027newWithOld\u0027 certificate, the new root CA\\ncertificate signed with the old root CA key, is provided, and verifying its\\nsignature is crucial for transferring the trust from the old CA key to the\\nnew one.\\n\\nThe \u0027id-it-rootCaKeyUpdate\u0027 messages are expected to be processed with\\nOSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the \u0027newWithOld\u0027\\ncertificate.  A typo in the certificate chain building code led to adding\\nan incorrect certificate (\u0027newWithOld\u0027 instead of \u0027oldRoot\u0027) to the\\ncertificate chain, rendering the certificate verification process ineffectual\\n(only the issuer name and the algorithm OIDs were verified by other parts\\nof the verification code).\\n\\nAn attacker who already has credentials that satisfy the CMP message\\nprotection checks can generate a new key pair and use a crafted self-signed\\ncertificate in its \u0027id-it-rootCaKeyUpdate\u0027 CMP messages which affected CMP\\nclients would accept as a new trust anchor.\\n\\nSignificant preconditions for the attack (having valid RA-level credentials)\\nare the reason the issue was assigned Low severity.\\n\\nThe FIPS modules are not affected by this issue, as the affected code is\\noutside the OpenSSL FIPS module boundary.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Issue Summary: An error in the callback used to verify the certificate\u003cbr\u003eprovided in a Root CA key update Certificate Management Protocol (CMP)\u003cbr\u003emessage response rendered the certificate validation ineffectual, which\u003cbr\u003ecould lead to escalation of credentials from the Registration Authority (RA)\u003cbr\u003elevel to the root Certification Authority (root CA) level.\u003cbr\u003e\u003cbr\u003eImpact Summary: The Registration Autority could replace the root CA\u003cbr\u003ecertificate for the CMP clients with an arbitrary root CA certificate.\u003cbr\u003e\u003cbr\u003eOne of the parts of the Certificate Management Protocol (CMP), specified in\u003cbr\u003eRFC 9810, is Root Certification Authority (root CA) key Rollover,\u003cbr\u003ewhich is sent by the server in a message with type \u0027id-it-rootCaKeyUpdate\u0027.\u003cbr\u003eAs part of these messages, \u0027newWithOld\u0027 certificate, the new root CA\u003cbr\u003ecertificate signed with the old root CA key, is provided, and verifying its\u003cbr\u003esignature is crucial for transferring the trust from the old CA key to the\u003cbr\u003enew one.\u003cbr\u003e\u003cbr\u003eThe \u0027id-it-rootCaKeyUpdate\u0027 messages are expected to be processed with\u003cbr\u003eOSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the \u0027newWithOld\u0027\u003cbr\u003ecertificate.  A typo in the certificate chain building code led to adding\u003cbr\u003ean incorrect certificate (\u0027newWithOld\u0027 instead of \u0027oldRoot\u0027) to the\u003cbr\u003ecertificate chain, rendering the certificate verification process ineffectual\u003cbr\u003e(only the issuer name and the algorithm OIDs were verified by other parts\u003cbr\u003eof the verification code).\u003cbr\u003e\u003cbr\u003eAn attacker who already has credentials that satisfy the CMP message\u003cbr\u003eprotection checks can generate a new key pair and use a crafted self-signed\u003cbr\u003ecertificate in its \u0027id-it-rootCaKeyUpdate\u0027 CMP messages which affected CMP\u003cbr\u003eclients would accept as a new trust anchor.\u003cbr\u003e\u003cbr\u003eSignificant preconditions for the attack (having valid RA-level credentials)\u003cbr\u003eare the reason the issue was assigned Low severity.\u003cbr\u003e\u003cbr\u003eThe FIPS modules are not affected by this issue, as the affected code is\u003cbr\u003eoutside the OpenSSL FIPS module boundary.\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-295\", \"description\": \"CWE-295 Improper Certificate Validation\"}]}], \"providerMetadata\": {\"orgId\": \"3a12439a-ef3a-4c79-92e6-6081a721f1e5\", \"shortName\": \"openssl\", \"dateUpdated\": \"2026-06-10T07:48:06.084Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-42769\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-06-10T07:48:06.084Z\", \"dateReserved\": \"2026-04-29T09:22:27.969Z\", \"assignerOrgId\": \"3a12439a-ef3a-4c79-92e6-6081a721f1e5\", \"datePublished\": \"2026-06-09T16:03:28.999Z\", \"assignerShortName\": \"openssl\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.