Medium [CVE-2026-78323] JSSTrustManager does not verify NSS trust flags on CA certificates
This medium-severity Red Hat Linux advisory covers CVE-2026-78323 affecting Red Hat Certificate System 10, Red Hat Certificate System 11, Red Hat Enterprise Linux 10.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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. 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.
Red Hat severity: Moderate — CVSS 6.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N). Weakness: CWE-295.
Affected Red Hat products: Red Hat Certificate System 10; Red Hat Certificate System 11; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 9. Red Hat lists Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8 as not affected.
Will not fix / out of support: Red Hat Enterprise Linux 6.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.