# CVE-2026-78323: Jss: jss: jsstrustmanager does not verify nss trust flags on ca certificates

> Attackers can bypass TLS trust validation in JSS by exploiting missing NSS trust flag checks, enabling man-in-the-middle attacks in specific configurations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-78323, GHSA-vc6r-2f9f-w5j6, OESA-2026-4134, OESA-2026-4135, OESA-2026-4136, OESA-2026-4137, UBUNTU-CVE-2026-78323

## What is CVE-2026-78323?

CVE-2026-78323 is a medium-severity vulnerability in Red Hat Certificate System 10, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-78323?


## How do I fix CVE-2026-78323?

Apply the vendor's patch.

## Is CVE-2026-78323 being exploited?

There is no known exploitation of CVE-2026-78323 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78323 and fix it if it is affected.

What it is: CVE-2026-78323 is a medium-severity vulnerability in Red Hat Certificate System 10, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78323 in the wild and no public exploit code.

Affected product: Red Hat Certificate System 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78323/ (Markdown: https://insights.sbomify.com/CVE-2026-78323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78323
- OSV: https://osv.dev/vulnerability/CVE-2026-78323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78323/
Summaries are generated and may contain mistakes; the official description above is the record.