{
  "threat_severity" : "Moderate",
  "public_date" : "2026-08-24T09:07:55Z",
  "bugzilla" : {
    "description" : "jss: jss: JSSTrustManager does not verify NSS trust flags on CA certificates",
    "id" : "2521775",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2521775"
  },
  "cvss3" : {
    "cvss3_base_score" : "6.5",
    "cvss3_scoring_vector" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N",
    "status" : "draft"
  },
  "cwe" : "CWE-295",
  "details" : [ "A flaw was found in JSS (Java Security Services). The JSSTrustManager class does not verify NSS trust flags when validating CA certificates, allowing certificates present in the NSS database without TRUSTED_CA flags to be accepted as trust anchors for TLS connections. In non-default configurations where certificate revocation checking is disabled, this could allow a man-in-the-middle attacker to forge certificates accepted by PKI client connections.", "A flaw was found in JSS (Java Security Services). The JSSTrustManager class does not verify NSS trust flags when validating CA certificates, allowing certificates present in the NSS database without TRUSTED_CA flags to be accepted as trust anchors for TLS connections. In non-default configurations where certificate revocation checking is disabled, this could allow a man-in-the-middle attacker to forge certificates accepted by PKI client connections." ],
  "statement" : "This flaw exists in the JSSTrustManager class but is mitigated in default product configurations by the native revocation verification check. Exploitation requires non-default configuration changes (disabling certificate revocation verification) that are not documented or recommended. The server-side TLS validation path (TomcatJSS) uses a different trust manager (JSSNativeTrustManager) that properly delegates to NSS native verification and is not affected.",
  "acknowledgement" : "This issue was discovered by Marco Fargetta (Red Hat).",
  "package_state" : [ {
    "product_name" : "Red Hat Certificate System 10",
    "fix_state" : "Fix deferred",
    "package_name" : "redhat-pki:10/jss",
    "cpe" : "cpe:/a:redhat:certificate_system:10"
  }, {
    "product_name" : "Red Hat Certificate System 11",
    "fix_state" : "Fix deferred",
    "package_name" : "jss",
    "cpe" : "cpe:/a:redhat:certificate_system:11"
  }, {
    "product_name" : "Red Hat Enterprise Linux 10",
    "fix_state" : "Fix deferred",
    "package_name" : "jss",
    "cpe" : "cpe:/o:redhat:enterprise_linux:10"
  }, {
    "product_name" : "Red Hat Enterprise Linux 6",
    "fix_state" : "Out of support scope",
    "package_name" : "jss",
    "cpe" : "cpe:/o:redhat:enterprise_linux:6"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "jss",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "pki-core:10.6/jss",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Fix deferred",
    "package_name" : "jss",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2026-78323\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-78323" ],
  "name" : "CVE-2026-78323",
  "mitigation" : {
    "value" : "In default configurations, this flaw is mitigated by the native revocation verification check (certChainRevokeVerify) which is enabled by default on PKI client connections. Ensure that certificate revocation verification remains enabled (do not set isCertRevocationVerify to false). On the server side, the default TomcatJSS configuration uses JSSNativeTrustManager which is not affected by this flaw.",
    "lang" : "en:us"
  },
  "csaw" : false
}