# CVE-2026-11873: Information disclosure in Red Hat Certificate System 9

> Unauthenticated attackers can trigger Java stack trace disclosures and log amplification via malformed requests to the Dogtag CA REST endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-q8f6-8cj7-hxqf

## What is CVE-2026-11873?

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

### Official description

An Apache-proxied Dogtag CA REST endpoint exposed by IdM (POST /ca/rest/certrequests) returns HTTP 500 with internal Java stack traces for unauthenticated malformed requests. The same unauthenticated error path emits large multi-line stack traces into the CA debug log, creating a log-amplification resource exhaustion vector (disk growth and I/O contention) without requiring authentication.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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


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

No fix has been published for CVE-2026-11873 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11873 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11873 is a medium-severity vulnerability in Red Hat Certificate System 9, published on 1 Sep 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-11873 in the wild and no public exploit code.

Affected product: Red Hat Certificate System 9. 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-11873/ (Markdown: https://insights.sbomify.com/CVE-2026-11873/index.md)
```

## Sources

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

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