# CVE-2026-17039: Missing authorization in Red Hat Certificate System 10

> An authenticated user can renew certificates in unauthorized realms due to a missing authorization check in the CA renewal path.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 25 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-17039, GHSA-jq46-23h4-vfpj, UBUNTU-CVE-2026-17039

## What is CVE-2026-17039?

CVE-2026-17039 is a low-severity missing authorization vulnerability in Red Hat Certificate System 10, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in pki-core. The certificate authority (CA) renewal request path does not perform the realm-based authorization check that the enrollment path performs, allowing an authenticated user entitled to one realm to cause a certificate belonging to a different realm to be renewed without that realm's authorization.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-17039 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17039 is a low-severity missing authorization vulnerability in Red Hat Certificate System 10, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17039 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-17039/ (Markdown: https://insights.sbomify.com/CVE-2026-17039/index.md)
```

## Sources

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

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