Common Weakness Enumeration

CWE-295

Allowed

Improper Certificate Validation

Abstraction: Base · Status: Draft

The product does not validate, or incorrectly validates, a certificate.

2540 vulnerabilities reference this CWE, most recent first.

CVE-2026-129888 (GCVE-0-2026-129888)

Vulnerability from cvelistv5 – Published: 2026-11-16 14:19 – Updated: 2026-11-16 14:19
VLAI
Title
Cetmix Tower through 17.0.3.0.0 and 18.0 before 18.0.4.0.1 Improper SSH Host Key Verification
Summary
Cetmix Tower through 17.0.3.0.0 and 18.0 before 18.0.4.0.1 contains an improper SSH host key verification vulnerability in SSHConnection.connect() that falls back to Paramiko's AutoAddPolicy when no host key is pinned. On-path attackers using ARP or DNS spoofing can present their own host key during Skip Host Key or Get from Host connections to capture stored SSH passwords and tamper with commands and files.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Cetmix Cetmix Tower Affected: 0 , ≤ 17.0.3.0.0 (custom)
Affected: 18.0 , < 18.0.4.0.1 (custom)
Create a notification for this product.
Date Public
2026-11-09 11:14
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:github/cetmix/cetmix-tower",
          "product": "Cetmix Tower",
          "repo": "https://github.com/cetmix/cetmix-tower",
          "vendor": "Cetmix",
          "versions": [
            {
              "lessThanOrEqual": "17.0.3.0.0",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "lessThan": "18.0.4.0.1",
              "status": "affected",
              "version": "18.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Tommaso Bona (ParzivalHack)"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Ivan Sokolov"
        }
      ],
      "datePublic": "2026-11-09T11:14:08.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Cetmix Tower through 17.0.3.0.0 and 18.0 before 18.0.4.0.1 contains an improper SSH host key verification vulnerability in SSHConnection.connect() that falls back to Paramiko\u0027s AutoAddPolicy when no host key is pinned. On-path attackers using ARP or DNS spoofing can present their own host key during Skip Host Key or Get from Host connections to capture stored SSH passwords and tamper with commands and files."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "ADJACENT",
            "baseScore": 7.6,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-16T14:19:14.646Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-q88c-38jh-8936)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/cetmix/cetmix-tower/security/advisories/GHSA-q88c-38jh-8936"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/cetmix/cetmix-tower/commit/3665d4cc324cefbe0d00109e0031a586d5fad5e7"
        },
        {
          "tags": [
            "issue-tracking",
            "patch"
          ],
          "url": "https://github.com/cetmix/cetmix-tower/pull/515"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/cetmix/cetmix-tower/blob/ce7715e7b9f2046ae86f54d1f4b4f2eab2499b0f/cetmix_tower_server/ssh/ssh.py#L91-L120"
        },
        {
          "name": "VulnCheck Advisory: Cetmix Tower through 17.0.3.0.0 and 18.0 before 18.0.4.0.1 Improper SSH Host Key Verification",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/cetmix-tower-through-17.0.3.0.0-and-18.0-before-18.0.4.0.1-improper-ssh-host-key-verification"
        }
      ],
      "title": "Cetmix Tower through 17.0.3.0.0 and 18.0 before 18.0.4.0.1 Improper SSH Host Key Verification",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-129888",
    "datePublished": "2026-11-16T14:19:14.646Z",
    "dateReserved": "2026-11-16T12:35:07.922Z",
    "dateUpdated": "2026-11-16T14:19:14.646Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129482 (GCVE-0-2026-129482)

Vulnerability from cvelistv5 – Published: 2026-11-15 13:47 – Updated: 2026-11-15 13:47
VLAI
Title
OkHttp through 5.5.1 Certificate Pinning Bypass via Trailing-Dot Hostname
Summary
OkHttp through 5.5.1 contains an improper certificate validation vulnerability in CertificatePinner that skips pin checks because Pin.matchesHostname does not normalize trailing-dot hostnames. Network attackers with a CA-trusted certificate not matching configured pins can intercept or modify TLS traffic when applications request the trailing-dot form of pinned hosts.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Square OkHttp Affected: 0 , ≤ 5.5.1 (semver)
    cpe:2.3:a:squareup:okhttp:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-08-22 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:maven/com.squareup.okhttp3/okhttp",
          "product": "OkHttp",
          "repo": "https://github.com/lysine-dev/okhttp",
          "vendor": "Square",
          "versions": [
            {
              "lessThanOrEqual": "5.5.1",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:squareup:okhttp:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "5.5.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Joshua Rogers"
        }
      ],
      "datePublic": "2026-08-22T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "OkHttp through 5.5.1 contains an improper certificate validation vulnerability in CertificatePinner that skips pin checks because Pin.matchesHostname does not normalize trailing-dot hostnames. Network attackers with a CA-trusted certificate not matching configured pins can intercept or modify TLS traffic when applications request the trailing-dot form of pinned hosts."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-15T13:47:24.248Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "tags": [
            "issue-tracking"
          ],
          "url": "https://github.com/lysine-dev/okhttp/issues/9724"
        },
        {
          "tags": [
            "patch",
            "issue-tracking"
          ],
          "url": "https://github.com/lysine-dev/okhttp/pull/9734"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/lysine-dev/okhttp/commit/30aa589761a9b4f5fe84c00e21e5ab44b22bd7c1"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/lysine-dev/okhttp/blob/parent-5.5.1/okhttp/src/commonJvmAndroid/kotlin/okhttp3/CertificatePinner.kt#L293-L314"
        },
        {
          "name": "VulnCheck Advisory: OkHttp through 5.5.1 Certificate Pinning Bypass via Trailing-Dot Hostname",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/okhttp-through-5.5.1-certificate-pinning-bypass-via-trailing-dot-hostname"
        }
      ],
      "title": "OkHttp through 5.5.1 Certificate Pinning Bypass via Trailing-Dot Hostname",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-129482",
    "datePublished": "2026-11-15T13:47:24.248Z",
    "dateReserved": "2026-11-15T13:41:09.589Z",
    "dateUpdated": "2026-11-15T13:47:24.248Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126621 (GCVE-0-2026-126621)

Vulnerability from cvelistv5 – Published: 2026-11-11 08:36 – Updated: 2026-11-11 08:36
VLAI
Title
Improper Certificate Validation in hMailServer
Summary
Progressive Robot hMailServer 6.0.0-B1 through 6.3.7 on Windows hands OpenSSL the names of its own TLS files - the listeners' certificates, chains, private keys and Diffie-Hellman parameters, a port's client-certificate CA file (from 6.2.19), the object store's CA file (from 6.3.4) and the ACME client's keys and certificates - as Latin-1 bytes, which on code page 1252 are the code page's own for U+00A0 to U+00FF, and OpenSSL's file opening on Windows reads a name as UTF-8 first and opens the file at that reading when it is there, or creates it there when its folder is. When every byte of a configured name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9, which are U+00E9 in UTF-8 - the server used the file at that other name whenever one was there, which allows a local attacker who can create that file or its folder but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, to have a port that logs on by client certificate (from 6.2.25) accept certificates from a certificate authority of the attacker's own and so sign in over the network as any mailbox without its password; to have the server trust such an authority for its object store and, intercepting that connection, read and modify the messages it stores; to receive the private keys the ACME client writes, the key of a certificate issued for the server's names among them; or to keep TLS ports from starting. The configuration is not the default: by default these files have names in ASCII, client certificates are off on every port, and the object store and ACME are off. The Linux builds are not affected.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Progressive Robot Ltd hMailServer Affected: 6.0.0-B1 , ≤ 6.3.7 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "hMailServer",
          "repo": "https://gitlab.com/hmailserver/hmailserver",
          "vendor": "Progressive Robot Ltd",
          "versions": [
            {
              "lessThanOrEqual": "6.3.7",
              "status": "affected",
              "version": "6.0.0-B1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Found by the hMailServer project (Progressive Robot Ltd)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Progressive Robot hMailServer 6.0.0-B1 through 6.3.7 on Windows hands OpenSSL the names of its own TLS files - the listeners\u0027 certificates, chains, private keys and Diffie-Hellman parameters, a port\u0027s client-certificate CA file (from 6.2.19), the object store\u0027s CA file (from 6.3.4) and the ACME client\u0027s keys and certificates - as Latin-1 bytes, which on code page 1252 are the code page\u0027s own for U+00A0 to U+00FF, and OpenSSL\u0027s file opening on Windows reads a name as UTF-8 first and opens the file at that reading when it is there, or creates it there when its folder is. When every byte of a configured name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9, which are U+00E9 in UTF-8 - the server used the file at that other name whenever one was there, which allows a local attacker who can create that file or its folder but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, to have a port that logs on by client certificate (from 6.2.25) accept certificates from a certificate authority of the attacker\u0027s own and so sign in over the network as any mailbox without its password; to have the server trust such an authority for its object store and, intercepting that connection, read and modify the messages it stores; to receive the private keys the ACME client writes, the key of a certificate issued for the server\u0027s names among them; or to keep TLS ports from starting. The configuration is not the default: by default these files have names in ASCII, client certificates are off on every port, and the object store and ACME are off. The Linux builds are not affected."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295: Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T08:36:26.283Z",
        "orgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
        "shortName": "GitLab"
      },
      "references": [
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/work_items/115"
        },
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade to hMailServer 6.3.8, which on Windows hands OpenSSL the name of each of these files in the code page and refuses, with HM7536 in the error log, a name with a character the code page does not have or whose bytes outside ASCII also read as UTF-8, so that nothing is read from or written to a refused file: a listener whose certificate or key file is refused does not start, a refused client-certificate CA file verifies no certificate, the object store\u0027s refused CA file allows no request, and the ACME client orders no certificate. Until then, name every TLS file, the ACME directory and the program and data folders by paths in ASCII alone, which read as the same name in the code page and in UTF-8 and which every affected version hands over unchanged; where a name outside ASCII must stay, keep each of its characters at or below U+00FF and one the system code page writes as its Latin-1 byte (on code page 1252, U+00A0 to U+00FF; none under a UTF-8 code page) - change any other name to ASCII - and make sure no one else can create the file or folder that the name\u0027s UTF-8 reading names."
        }
      ],
      "title": "Improper Certificate Validation in hMailServer"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
    "assignerShortName": "GitLab",
    "cveId": "CVE-2026-126621",
    "datePublished": "2026-11-11T08:36:26.283Z",
    "dateReserved": "2026-11-11T08:30:22.140Z",
    "dateUpdated": "2026-11-11T08:36:26.283Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126611 (GCVE-0-2026-126611)

Vulnerability from cvelistv5 – Published: 2026-11-11 08:30 – Updated: 2026-11-11 08:30
VLAI
Title
Improper Certificate Validation in hMailServer
Summary
Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database, TlsMode=verify-full and no TlsCaFile, does not verify the database server's certificate's issuer or name when the connection is one that MariaDB Connector/C treats as local - Server= set to 127.0.0.1, ::1 or localhost (on Linux a Unix socket), to . on Windows (a named pipe), or to a comma-separated list of servers that holds such an element - which allows a local attacker who can stand in for the database server, for example by listening on its port while it is stopped or restarting, to receive the database sign-in, the password included, and to read and modify the traffic between hMailServer and its database. hMailServer applied verify-full by turning the client's certificate verification on without a CA file, but MariaDB Connector/C 3.4.1 and later, on a connection they treat as local and with no CA file, accept any certificate within its validity period that is self-signed or sent with its own root, for any name (Connector/C 3.4.2 to 3.4.10 also one whose issuer they cannot find), so the client accepted the certificate an impostor made, asked no proof of the password and allowed a switch to an authentication method that sends the password unhashed, while hmailserver --check-database said the certificate had been checked against the system's trust store and the application log that it had been checked. The Windows builds bundle Connector/C 3.4.9 (6.3.4 to 6.3.6) and 3.4.11 (6.3.7); on Linux the distribution's client is used, and Connector/C 3.3 and 3.4.0 and Oracle's MySQL client are not affected. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Progressive Robot Ltd hMailServer Affected: 6.3.4 , ≤ 6.3.7 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "hMailServer",
          "repo": "https://gitlab.com/hmailserver/hmailserver",
          "vendor": "Progressive Robot Ltd",
          "versions": [
            {
              "lessThanOrEqual": "6.3.7",
              "status": "affected",
              "version": "6.3.4",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Found by the hMailServer project (Progressive Robot Ltd)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database, TlsMode=verify-full and no TlsCaFile, does not verify the database server\u0027s certificate\u0027s issuer or name when the connection is one that MariaDB Connector/C treats as local - Server= set to 127.0.0.1, ::1 or localhost (on Linux a Unix socket), to . on Windows (a named pipe), or to a comma-separated list of servers that holds such an element - which allows a local attacker who can stand in for the database server, for example by listening on its port while it is stopped or restarting, to receive the database sign-in, the password included, and to read and modify the traffic between hMailServer and its database. hMailServer applied verify-full by turning the client\u0027s certificate verification on without a CA file, but MariaDB Connector/C 3.4.1 and later, on a connection they treat as local and with no CA file, accept any certificate within its validity period that is self-signed or sent with its own root, for any name (Connector/C 3.4.2 to 3.4.10 also one whose issuer they cannot find), so the client accepted the certificate an impostor made, asked no proof of the password and allowed a switch to an authentication method that sends the password unhashed, while hmailserver --check-database said the certificate had been checked against the system\u0027s trust store and the application log that it had been checked. The Windows builds bundle Connector/C 3.4.9 (6.3.4 to 6.3.6) and 3.4.11 (6.3.7); on Linux the distribution\u0027s client is used, and Connector/C 3.3 and 3.4.0 and Oracle\u0027s MySQL client are not affected. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "HIGH",
            "baseScore": 7,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295: Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T08:30:32.132Z",
        "orgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
        "shortName": "GitLab"
      },
      "references": [
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/work_items/113"
        },
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade to hMailServer 6.3.8, which reads Server= as MariaDB Connector/C does and refuses TlsMode=verify-full with no TlsCaFile before connecting, with HM7535 in the error log, on a connection the client treats as local or a Server= list that holds one, and which says, on such a connection with a TlsCaFile, that the certificate\u0027s issuer was checked and not its name. Until then, set TlsCaFile to a file holding only the CA that issues the database server\u0027s certificate, at a path in ASCII alone; the client then checks the certificate\u0027s issuer on such a connection, though not its name. On these versions the --check-database settings line and the application log say the certificate was checked either way, so they do not show the difference."
        }
      ],
      "title": "Improper Certificate Validation in hMailServer"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
    "assignerShortName": "GitLab",
    "cveId": "CVE-2026-126611",
    "datePublished": "2026-11-11T08:30:32.132Z",
    "dateReserved": "2026-11-11T08:04:34.376Z",
    "dateUpdated": "2026-11-11T08:30:32.132Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126610 (GCVE-0-2026-126610)

Vulnerability from cvelistv5 – Published: 2026-11-11 08:30 – Updated: 2026-11-11 08:30
VLAI
Title
Improper Certificate Validation in hMailServer
Summary
Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database and TlsMode=verify-full, does not hand the database client the CA file that TlsCaFile names when the file's name contains a character outside ASCII on Linux, or above U+00FF on Windows, which allows an attacker who can intercept the connection to the database server to read and modify the traffic between hMailServer and its database, by presenting, with MariaDB Connector/C 3.4.2 to 3.4.10 as the client, a certificate from any authority, its own included, for any name, and otherwise a certificate for the database server's name issued by any certificate authority in the system's trust store. The server converted the name for the client with the C runtime's conversion in the C locale, which gives an empty string for such a name, and then set no CA file at all, without an error, while certificate verification stayed on, so the client - MariaDB Connector/C, bundled on Windows and the distribution's on Linux - verified the certificate of a database server over the network against the system's trust store instead of the configured CA; Connector/C 3.4.2 to 3.4.10 (bundled on Windows in 6.3.4 to 6.3.6) went further and, with no CA file, took a certificate within its dates whose issuer it could not find, for any name, with neither its chain nor its name checked and no password proof, when the server offered first a sign-in method that hashes the password, which an attacker in the middle chooses (MariaDB's CONC-853, fixed in Connector/C 3.4.11), and Connector/C 3.4 accepted from a MariaDB 11.4 or later server a certificate the store did not vouch for when that server proved it held the account's password; on a connection it treats as local (127.0.0.1, ::1, a Unix socket, a named pipe, and localhost on Windows), Connector/C 3.4.1 and later checked neither the certificate's issuer nor its name, so that a local attacker able to stand in for the database server could present any certificate within its dates of its own making. The settings line of hmailserver --check-database still named the configured file, and the application log said the certificate had been checked. With MariaDB Connector/C 3.4.1 to 3.4.9 as the client - bundled on Windows in 6.3.4 to 6.3.6, and the client of Linux distributions that have not patched it - the missing CA file also met the precondition of CVE-2026-107819, so that a certificate issued for any other name by a trusted authority was enough to obtain the database password. On Linux the file was found only when the server ran on glibc under a locale whose character set holds the name's characters (a UTF-8 locale, or a legacy 8-bit one the system has, in whose bytes the file is then named); with no locale, LC_ALL=C or a locale the system lacks, and on Alpine (musl), the connection failed instead. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Progressive Robot Ltd hMailServer Affected: 6.3.4 , ≤ 6.3.7 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "hMailServer",
          "repo": "https://gitlab.com/hmailserver/hmailserver",
          "vendor": "Progressive Robot Ltd",
          "versions": [
            {
              "lessThanOrEqual": "6.3.7",
              "status": "affected",
              "version": "6.3.4",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Found by the hMailServer project (Progressive Robot Ltd)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database and TlsMode=verify-full, does not hand the database client the CA file that TlsCaFile names when the file\u0027s name contains a character outside ASCII on Linux, or above U+00FF on Windows, which allows an attacker who can intercept the connection to the database server to read and modify the traffic between hMailServer and its database, by presenting, with MariaDB Connector/C 3.4.2 to 3.4.10 as the client, a certificate from any authority, its own included, for any name, and otherwise a certificate for the database server\u0027s name issued by any certificate authority in the system\u0027s trust store. The server converted the name for the client with the C runtime\u0027s conversion in the C locale, which gives an empty string for such a name, and then set no CA file at all, without an error, while certificate verification stayed on, so the client - MariaDB Connector/C, bundled on Windows and the distribution\u0027s on Linux - verified the certificate of a database server over the network against the system\u0027s trust store instead of the configured CA; Connector/C 3.4.2 to 3.4.10 (bundled on Windows in 6.3.4 to 6.3.6) went further and, with no CA file, took a certificate within its dates whose issuer it could not find, for any name, with neither its chain nor its name checked and no password proof, when the server offered first a sign-in method that hashes the password, which an attacker in the middle chooses (MariaDB\u0027s CONC-853, fixed in Connector/C 3.4.11), and Connector/C 3.4 accepted from a MariaDB 11.4 or later server a certificate the store did not vouch for when that server proved it held the account\u0027s password; on a connection it treats as local (127.0.0.1, ::1, a Unix socket, a named pipe, and localhost on Windows), Connector/C 3.4.1 and later checked neither the certificate\u0027s issuer nor its name, so that a local attacker able to stand in for the database server could present any certificate within its dates of its own making. The settings line of hmailserver --check-database still named the configured file, and the application log said the certificate had been checked. With MariaDB Connector/C 3.4.1 to 3.4.9 as the client - bundled on Windows in 6.3.4 to 6.3.6, and the client of Linux distributions that have not patched it - the missing CA file also met the precondition of CVE-2026-107819, so that a certificate issued for any other name by a trusted authority was enough to obtain the database password. On Linux the file was found only when the server ran on glibc under a locale whose character set holds the name\u0027s characters (a UTF-8 locale, or a legacy 8-bit one the system has, in whose bytes the file is then named); with no locale, LC_ALL=C or a locale the system lacks, and on Alpine (musl), the connection failed instead. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.4,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295: Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T08:30:37.134Z",
        "orgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
        "shortName": "GitLab"
      },
      "references": [
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/work_items/112"
        },
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade to hMailServer 6.3.8, which hands the database client the CA file\u0027s name in the encoding the client opens it in - UTF-8 on Linux whatever the locale, the ANSI code page on Windows - and refuses before connecting, with HM7534 in the error log, a name it cannot write so, never handing over an empty one. Until then, give TlsCaFile a path in ASCII alone, which every affected version hands to the client as it is; on these versions the settings line of hmailserver --check-database names the configured file whether or not the client was given it, so it does not show the difference. On Linux, also update the distribution\u0027s MariaDB Connector/C to 3.4.11 or later, which fixes both CVE-2026-107819 and CONC-853, where one is offered; a version with the fix for CVE-2026-107819 alone still accepts a certificate whose issuer it cannot find."
        }
      ],
      "title": "Improper Certificate Validation in hMailServer"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
    "assignerShortName": "GitLab",
    "cveId": "CVE-2026-126610",
    "datePublished": "2026-11-11T08:30:37.134Z",
    "dateReserved": "2026-11-11T08:04:29.376Z",
    "dateUpdated": "2026-11-11T08:30:37.134Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126609 (GCVE-0-2026-126609)

Vulnerability from cvelistv5 – Published: 2026-11-11 08:30 – Updated: 2026-11-11 08:30
VLAI
Title
Improper Certificate Validation in hMailServer
Summary
Progressive Robot hMailServer 6.2.25 through 6.3.7 on Windows, with a PostgreSQL database, the connection's sslmode require, verify-ca or verify-full, and a root certificate file named by PostgreSQLSslRootCert (from 6.2.25) or, with TlsMode=verify-full and neither PostgreSQL key set, by TlsCaFile (from 6.3.4), hands the file's name to libpq as bytes in the system's ANSI code page (up to 6.3.5 as Latin-1 bytes, which on code page 1252 are the code page's own for U+00A0 to U+00FF), and libpq looks for the file by those bytes and then hands the same bytes to OpenSSL, whose file opening on Windows reads a name as UTF-8 first and opens the file at that reading when one is there. When every byte of the name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9 on code page 1252, which are U+00E9 in UTF-8 - the database server's certificate was checked against the file at that other name whenever one was there, which allows a local attacker who can create that file but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, or beside a folder directly under the system drive's root whose permissions the administrator restricted, and who can intercept the connection to the database server or stand in for it, to have hMailServer trust a certificate authority of the attacker's own and read and modify the traffic between hMailServer and its database, the database password included; the file alone, holding no authority that issued the database server's certificate, stops hMailServer from connecting to its database. The same applies in 6.3.4 through 6.3.7 to TlsCaFile when an Oracle MySQL client library has been put in place of the bundled MariaDB Connector/C, since that client opens the file through OpenSSL in the same way; the bundled MariaDB Connector/C opens the file in the code page and is not affected, and neither are the Linux builds. The configuration is not the default: by default no root certificate file is named.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
Progressive Robot Ltd hMailServer Affected: 6.2.25 , ≤ 6.3.7 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "hMailServer",
          "repo": "https://gitlab.com/hmailserver/hmailserver",
          "vendor": "Progressive Robot Ltd",
          "versions": [
            {
              "lessThanOrEqual": "6.3.7",
              "status": "affected",
              "version": "6.2.25",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Found by the hMailServer project (Progressive Robot Ltd)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Progressive Robot hMailServer 6.2.25 through 6.3.7 on Windows, with a PostgreSQL database, the connection\u0027s sslmode require, verify-ca or verify-full, and a root certificate file named by PostgreSQLSslRootCert (from 6.2.25) or, with TlsMode=verify-full and neither PostgreSQL key set, by TlsCaFile (from 6.3.4), hands the file\u0027s name to libpq as bytes in the system\u0027s ANSI code page (up to 6.3.5 as Latin-1 bytes, which on code page 1252 are the code page\u0027s own for U+00A0 to U+00FF), and libpq looks for the file by those bytes and then hands the same bytes to OpenSSL, whose file opening on Windows reads a name as UTF-8 first and opens the file at that reading when one is there. When every byte of the name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9 on code page 1252, which are U+00E9 in UTF-8 - the database server\u0027s certificate was checked against the file at that other name whenever one was there, which allows a local attacker who can create that file but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, or beside a folder directly under the system drive\u0027s root whose permissions the administrator restricted, and who can intercept the connection to the database server or stand in for it, to have hMailServer trust a certificate authority of the attacker\u0027s own and read and modify the traffic between hMailServer and its database, the database password included; the file alone, holding no authority that issued the database server\u0027s certificate, stops hMailServer from connecting to its database. The same applies in 6.3.4 through 6.3.7 to TlsCaFile when an Oracle MySQL client library has been put in place of the bundled MariaDB Connector/C, since that client opens the file through OpenSSL in the same way; the bundled MariaDB Connector/C opens the file in the code page and is not affected, and neither are the Linux builds. The configuration is not the default: by default no root certificate file is named."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295: Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T08:30:17.425Z",
        "orgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
        "shortName": "GitLab"
      },
      "references": [
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/work_items/114"
        },
        {
          "url": "https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade to hMailServer 6.3.8, which on Windows refuses before connecting, with HM7534 in the error log, a root certificate file name whose bytes in the code page outside ASCII also read as UTF-8, for PostgreSQLSslRootCert and TlsCaFile alike and whichever database client is loaded, and hands an Oracle MySQL client the name in UTF-8, which names the same file. Until then, name the root certificate file by a path in ASCII alone, which reads as the same name in the code page and in UTF-8 and which every affected version hands over unchanged; where a name outside ASCII must stay, make sure no one else can create the file or folder that the name\u0027s UTF-8 reading names."
        }
      ],
      "title": "Improper Certificate Validation in hMailServer"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ceab7361-8a18-47b1-92ba-4d7d25f6715a",
    "assignerShortName": "GitLab",
    "cveId": "CVE-2026-126609",
    "datePublished": "2026-11-11T08:30:17.425Z",
    "dateReserved": "2026-11-11T08:04:24.373Z",
    "dateUpdated": "2026-11-11T08:30:17.425Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126232 (GCVE-0-2026-126232)

Vulnerability from cvelistv5 – Published: 2026-11-11 21:30 – Updated: 2026-11-16 09:16
VLAI
Summary
A improper certificate validation vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer Cloud 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11 may allow a MITM attacker to impersonate the radius server via a rogue RADIUS server.
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-12 00:00 UTC
CWE
  • CWE-295 - Improper access control
References
Impacted products
Vendor Product Version
Fortinet FortiManager Affected: 8.0.0 , ≤ 8.0.1 (semver)
Affected: 7.6.0 , ≤ 7.6.7 (semver)
Affected: 7.4.0 , ≤ 7.4.11 (semver)
    cpe:2.3:o:fortinet:fortimanager:8.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:8.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.6.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.11:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.10:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.9:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.8:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortimanager:7.4.0:*:*:*:*:*:*:*
Create a notification for this product.
Fortinet FortiAnalyzer Affected: 8.0.0 , ≤ 8.0.1 (semver)
Affected: 7.6.0 , ≤ 7.6.7 (semver)
Affected: 7.4.0 , ≤ 7.4.11 (semver)
    cpe:2.3:o:fortinet:fortianalyzer:8.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:8.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.6.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.11:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.10:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.9:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.8:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortianalyzer:7.4.0:*:*:*:*:*:*:*
Create a notification for this product.
Fortinet FortiAnalyzer Cloud Affected: 8.0.1
Affected: 7.6.0 , ≤ 7.6.7 (semver)
Affected: 7.4.1 , ≤ 7.4.11 (semver)
    cpe:2.3:a:fortinet:fortianalyzercloud:8.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortianalyzercloud:7.4.1:*:*:*:*:*:*:*
Create a notification for this product.
Fortinet FortiManager Cloud Affected: 8.0.1
Affected: 7.6.0 , ≤ 7.6.7 (semver)
Affected: 7.4.1 , ≤ 7.4.11 (semver)
    cpe:2.3:a:fortinet:fortimanagercloud:8.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortimanagercloud:7.4.1:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126232",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-12T00:00:00+00:00",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T05:00:59.058Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:o:fortinet:fortimanager:8.0.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:8.0.0:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.7:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.6:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.5:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.4:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.3:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.2:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.6.0:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.11:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.10:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.9:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.8:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.7:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.6:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.5:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.4:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.3:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.2:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortimanager:7.4.0:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "FortiManager",
          "vendor": "Fortinet",
          "versions": [
            {
              "lessThanOrEqual": "8.0.1",
              "status": "affected",
              "version": "8.0.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.6.7",
              "status": "affected",
              "version": "7.6.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.4.11",
              "status": "affected",
              "version": "7.4.0",
              "versionType": "semver"
            }
          ]
        },
        {
          "cpes": [
            "cpe:2.3:o:fortinet:fortianalyzer:8.0.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:8.0.0:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.7:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.6:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.5:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.4:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.3:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.2:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.6.0:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.11:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.10:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.9:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.8:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.7:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.6:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.5:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.4:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.3:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.2:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.1:*:*:*:*:*:*:*",
            "cpe:2.3:o:fortinet:fortianalyzer:7.4.0:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "FortiAnalyzer",
          "vendor": "Fortinet",
          "versions": [
            {
              "lessThanOrEqual": "8.0.1",
              "status": "affected",
              "version": "8.0.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.6.7",
              "status": "affected",
              "version": "7.6.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.4.11",
              "status": "affected",
              "version": "7.4.0",
              "versionType": "semver"
            }
          ]
        },
        {
          "cpes": [
            "cpe:2.3:a:fortinet:fortianalyzercloud:8.0.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.7:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.6:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.5:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.4:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.3:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.2:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.6.0:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.11:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.10:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.9:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.8:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.7:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.6:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.5:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.4:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.3:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.2:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortianalyzercloud:7.4.1:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "FortiAnalyzer Cloud",
          "vendor": "Fortinet",
          "versions": [
            {
              "status": "affected",
              "version": "8.0.1"
            },
            {
              "lessThanOrEqual": "7.6.7",
              "status": "affected",
              "version": "7.6.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.4.11",
              "status": "affected",
              "version": "7.4.1",
              "versionType": "semver"
            }
          ]
        },
        {
          "cpes": [
            "cpe:2.3:a:fortinet:fortimanagercloud:8.0.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.7:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.6:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.5:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.4:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.3:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.2:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.6.0:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.11:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.10:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.9:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.8:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.7:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.6:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.5:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.4:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.3:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.2:*:*:*:*:*:*:*",
            "cpe:2.3:a:fortinet:fortimanagercloud:7.4.1:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "FortiManager Cloud",
          "vendor": "Fortinet",
          "versions": [
            {
              "status": "affected",
              "version": "8.0.1"
            },
            {
              "lessThanOrEqual": "7.6.7",
              "status": "affected",
              "version": "7.6.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.4.11",
              "status": "affected",
              "version": "7.4.1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A improper certificate validation vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer Cloud 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11 may allow a MITM attacker to impersonate the radius server via a rogue RADIUS server."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "Improper access control",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-16T09:16:42.358Z",
        "orgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
        "shortName": "fortinet"
      },
      "references": [
        {
          "name": "https://fortiguard.fortinet.com/psirt/FG-IR-26-247",
          "url": "https://fortiguard.fortinet.com/psirt/FG-IR-26-247"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Upgrade to FortiManager version 8.0.2 or above\nUpgrade to FortiManager version 7.6.8 or above\nUpgrade to FortiManager version 7.4.12 or above\nUpgrade to FortiManager Cloud version 8.0.2 or above\nUpgrade to FortiManager Cloud version 7.6.8 or above\nUpgrade to FortiManager Cloud version 7.4.12 or above\nUpgrade to FortiAnalyzer version 8.0.2 or above\nUpgrade to FortiAnalyzer version 7.6.8 or above\nUpgrade to FortiAnalyzer version 7.4.12 or above\nUpgrade to FortiAnalyzer Cloud version 8.0.2 or above\nUpgrade to FortiAnalyzer Cloud version 7.6.8 or above\nUpgrade to FortiAnalyzer Cloud version 7.4.12 or above"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
    "assignerShortName": "fortinet",
    "cveId": "CVE-2026-126232",
    "datePublished": "2026-11-11T21:30:46.856Z",
    "dateReserved": "2026-11-10T20:09:13.512Z",
    "dateUpdated": "2026-11-16T09:16:42.358Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-125336 (GCVE-0-2026-125336)

Vulnerability from cvelistv5 – Published: 2026-11-10 18:52 – Updated: 2026-11-13 15:41
VLAI
Title
Forge: X.509 nameConstraints not enforced by verifyCertificateChain()
Summary
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths. A name-constrained certificate authority with a non-critical extension can therefore issue a leaf certificate with a subjectAltName dNSName or subject commonName outside a permitted subtree or inside an excluded subtree, and node-forge accepts the chain. Exploitation requires a name-constrained CA that chains to a trusted root and either its private key or the ability to obtain an out-of-scope certificate, allowing impersonation of names outside the delegated namespace, including against forge.tls clients. Chains without nameConstraints are not affected, and affected versions safely reject critical nameConstraints as unsupported rather than accepting them. This issue is fixed in version 1.4.3.
SSVC
Exploitation: poc Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 15:38 UTC
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
digitalbazaar forge Affected: < 1.4.3
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-125336",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T15:38:29.973125Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T15:41:15.447Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://github.com/digitalbazaar/forge/security/advisories/GHSA-3cc4-3294-vgjf"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "forge",
          "vendor": "digitalbazaar",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 1.4.3"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths. A name-constrained certificate authority with a non-critical extension can therefore issue a leaf certificate with a subjectAltName dNSName or subject commonName outside a permitted subtree or inside an excluded subtree, and node-forge accepts the chain. Exploitation requires a name-constrained CA that chains to a trusted root and either its private key or the ability to obtain an out-of-scope certificate, allowing impersonation of names outside the delegated namespace, including against forge.tls clients. Chains without nameConstraints are not affected, and affected versions safely reject critical nameConstraints as unsupported rather than accepting them. This issue is fixed in version 1.4.3."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.4,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295: Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-10T18:52:37.915Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/digitalbazaar/forge/security/advisories/GHSA-3cc4-3294-vgjf",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/digitalbazaar/forge/security/advisories/GHSA-3cc4-3294-vgjf"
        },
        {
          "name": "https://github.com/digitalbazaar/forge/pull/1169",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/digitalbazaar/forge/pull/1169"
        },
        {
          "name": "https://github.com/digitalbazaar/forge/commit/6b23eae8beac316b6867bdb0e7ad7c2c959a97f6",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/digitalbazaar/forge/commit/6b23eae8beac316b6867bdb0e7ad7c2c959a97f6"
        },
        {
          "name": "https://github.com/digitalbazaar/forge/commit/862aa5f630bdf40b0dfda408d6ac357bf35a7d6b",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/digitalbazaar/forge/commit/862aa5f630bdf40b0dfda408d6ac357bf35a7d6b"
        },
        {
          "name": "https://github.com/digitalbazaar/forge/releases/tag/v1.4.3",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/digitalbazaar/forge/releases/tag/v1.4.3"
        }
      ],
      "source": {
        "advisory": "GHSA-3cc4-3294-vgjf",
        "discovery": "UNKNOWN"
      },
      "title": "Forge: X.509 nameConstraints not enforced by verifyCertificateChain()"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-125336",
    "datePublished": "2026-11-10T18:52:37.915Z",
    "dateReserved": "2026-11-09T21:22:55.599Z",
    "dateUpdated": "2026-11-13T15:41:15.447Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-123877 (GCVE-0-2026-123877)

Vulnerability from cvelistv5 – Published: 2026-11-11 18:28 – Updated: 2026-11-11 18:28
VLAI
Title
Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse
Summary
A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
nodejs node Affected: 0.0.0 , < 22.23.5 (semver)
Affected: 23.0.0 , < 24.22.3 (semver)
Affected: 25.0.0 , < 26.13.1 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "node",
          "vendor": "nodejs",
          "versions": [
            {
              "lessThan": "22.23.5",
              "status": "affected",
              "version": "0.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "24.22.3",
              "status": "affected",
              "version": "23.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "26.13.1",
              "status": "affected",
              "version": "25.0.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "aegis1337 and mickeyjoe"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "mcollina"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "aduh95"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/markdown",
              "value": "A certificate validation bypass in Node.js `https.Agent` lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. `https.Agent.prototype.getName()` assigns the same Agent and session-cache key to a request that omits `ca` and one that explicitly supplies `ca: []`, because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting `ca` uses the default trust store, while supplying `ca` replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later `ca: []` policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports `authorized === true` and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x."
            }
          ],
          "value": "A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x."
        }
      ],
      "metrics": [
        {
          "cvssV3_0": {
            "baseScore": 6.8,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.0"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-11T18:28:38.494Z",
        "orgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
        "shortName": "openjs"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        },
        {
          "url": "https://cna.openjsf.org/security-advisories.html"
        }
      ],
      "title": "Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse",
      "x_generator": {
        "engine": "nodejs-private/security-release publish-cves"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
    "assignerShortName": "openjs",
    "cveId": "CVE-2026-123877",
    "datePublished": "2026-11-11T18:28:38.494Z",
    "dateReserved": "2026-11-06T16:32:30.304Z",
    "dateUpdated": "2026-11-11T18:28:38.494Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-123867 (GCVE-0-2026-123867)

Vulnerability from cvelistv5 – Published: 2026-11-11 18:23 – Updated: 2026-11-12 14:34
VLAI
Title
Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA
Summary
A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context's CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
CWE
  • CWE-295 - Improper Certificate Validation
Impacted products
Vendor Product Version
nodejs node Affected: 0.0.0 , < 22.23.5 (semver)
Affected: 23.0.0 , < 24.22.3 (semver)
Affected: 25.0.0 , < 26.13.1 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "node",
          "vendor": "nodejs",
          "versions": [
            {
              "lessThan": "22.23.5",
              "status": "affected",
              "version": "0.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "24.22.3",
              "status": "affected",
              "version": "23.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "26.13.1",
              "status": "affected",
              "version": "25.0.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Uttkarsh Singh"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "mcollina"
        },
        {
          "lang": "en",
          "type": "remediation reviewer",
          "value": "UlisesGascon"
        },
        {
          "lang": "en",
          "type": "remediation reviewer",
          "value": "pimterry"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "aduh95"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/markdown",
              "value": "A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context\u0027s CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x."
            }
          ],
          "value": "A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context\u0027s CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.2,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-295",
              "description": "CWE-295 Improper Certificate Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-12T14:34:33.702Z",
        "orgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
        "shortName": "openjs"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        },
        {
          "url": "https://cna.openjsf.org/security-advisories.html"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA",
      "x_generator": {
        "engine": "nodejs-private/security-release publish-cves"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
    "assignerShortName": "openjs",
    "cveId": "CVE-2026-123867",
    "datePublished": "2026-11-11T18:23:12.991Z",
    "dateReserved": "2026-11-06T16:16:19.081Z",
    "dateUpdated": "2026-11-12T14:34:33.702Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Mitigation
Architecture and Design Implementation

Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.

Mitigation
Implementation

If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

CAPEC-459: Creating a Rogue Certification Authority Certificate

An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.

CAPEC-475: Signature Spoofing by Improper Validation

An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.