CVE-2026-78323: Improper Certificate Validation in Red Hat Red Hat Certificate System 10
A vulnerability exists in JSS (Java Security Services) where the JSSTrustManager class does not verify NSS trust flags when validating CA certificates. This flaw allows certificates in the NSS database without TRUSTED_CA flags to be accepted as trust anchors for TLS connections. The issue is mitigated in default configurations by native certificate revocation verification, which is enabled by default. Exploitation requires disabling certificate revocation checking, a non-default and unsupported configuration. The server-side TLS validation using JSSNativeTrustManager is not affected.
AI Analysis
Technical Summary
CVE-2026-78323 is a vulnerability in the JSSTrustManager class of JSS where it fails to verify NSS trust flags on CA certificates during validation. This allows certificates present in the NSS database without TRUSTED_CA flags to be trusted as TLS trust anchors. In configurations where certificate revocation checking is disabled (non-default), this could enable a man-in-the-middle attacker to forge certificates accepted by PKI client connections. The flaw is mitigated by default because certificate revocation verification (certChainRevokeVerify) is enabled by default on PKI client connections. The server-side TLS validation path using JSSNativeTrustManager is unaffected as it properly delegates to NSS native verification.
Potential Impact
If exploited in non-default configurations where certificate revocation checking is disabled, an attacker could perform man-in-the-middle attacks by forging certificates accepted by PKI client connections. This could lead to confidentiality breaches. The flaw does not affect server-side TLS validation in default configurations. The overall impact is rated medium with high confidentiality impact, low integrity impact, and no availability impact.
Mitigation Recommendations
This vulnerability is mitigated in default product configurations by the native certificate revocation verification check, which is enabled by default. Users should ensure that certificate revocation verification remains enabled (do not disable isCertRevocationVerify). No action is required for server-side TLS validation using the default TomcatJSS configuration, which uses the unaffected JSSNativeTrustManager. There is no vendor advisory indicating an official patch release yet; patch status is not confirmed. Users should monitor the vendor advisory for updates on fixes.
CVE-2026-78323: Improper Certificate Validation in Red Hat Red Hat Certificate System 10
Description
A vulnerability exists in JSS (Java Security Services) where the JSSTrustManager class does not verify NSS trust flags when validating CA certificates. This flaw allows certificates in the NSS database without TRUSTED_CA flags to be accepted as trust anchors for TLS connections. The issue is mitigated in default configurations by native certificate revocation verification, which is enabled by default. Exploitation requires disabling certificate revocation checking, a non-default and unsupported configuration. The server-side TLS validation using JSSNativeTrustManager is not affected.
CVSS v3.1
Score 6.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-78323 is a vulnerability in the JSSTrustManager class of JSS where it fails to verify NSS trust flags on CA certificates during validation. This allows certificates present in the NSS database without TRUSTED_CA flags to be trusted as TLS trust anchors. In configurations where certificate revocation checking is disabled (non-default), this could enable a man-in-the-middle attacker to forge certificates accepted by PKI client connections. The flaw is mitigated by default because certificate revocation verification (certChainRevokeVerify) is enabled by default on PKI client connections. The server-side TLS validation path using JSSNativeTrustManager is unaffected as it properly delegates to NSS native verification.
Potential Impact
If exploited in non-default configurations where certificate revocation checking is disabled, an attacker could perform man-in-the-middle attacks by forging certificates accepted by PKI client connections. This could lead to confidentiality breaches. The flaw does not affect server-side TLS validation in default configurations. The overall impact is rated medium with high confidentiality impact, low integrity impact, and no availability impact.
Mitigation Recommendations
This vulnerability is mitigated in default product configurations by the native certificate revocation verification check, which is enabled by default. Users should ensure that certificate revocation verification remains enabled (do not disable isCertRevocationVerify). No action is required for server-side TLS validation using the default TomcatJSS configuration, which uses the unaffected JSSNativeTrustManager. There is no vendor advisory indicating an official patch release yet; patch status is not confirmed. Users should monitor the vendor advisory for updates on fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vc6r-2f9f-w5j6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-78323"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a8c4c32acd9273b499bc7d1
Added to database: 08/24/2026, 13:50:42 UTC
Last enriched: 08/24/2026, 13:52:15 UTC
Last updated: 08/24/2026, 15:51:59 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.