CVE-2026-80110
Pki-core: dogtag pki v2 rest acl filter's reverse-lexicographic tie-break lets a ca agent invoke the admin-only raw profile creation endpoint
What happened?
A flaw was found in pki-core. The v2 REST ACL filter selects a tie-breaking permission for colliding literal and wildcard ACL keys using lexicographic string comparison rather than specificity, causing a wildcard-mapped permission to override a more specific literal-mapped permission when both match. In the CA's profile-management REST API this allows a request to POST /v2/profiles/raw -- intended to require Administrator-level profiles.create permission -- to instead be authorized under the lower-privileged profiles.approve permission held by the default Certificate Manager Agents group. The highest threat from this vulnerability is to confidentiality and integrity of the certificate authority's issuance policy.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| dogtag-pkiRed Hat | unaffected: 0:11.9.0-5.el10_2 to < * | See vendor advisory |
| dogtag-pkiRed Hat | unaffected: 0:11.6.0-3.el10_0.1 to < * | See vendor advisory |
| pki-coreRed Hat | unaffected: 0:11.7.1-2.el9_8 to < * | See vendor advisory |
| pki-coreRed Hat | unaffected: 0:11.6.0-4.el9_6 to < * | See vendor advisory |
| pki-coreRed Hat | Default status: unaffected | See vendor advisory |
| pki-coreRed Hat | Default status: unknown | See vendor advisory |
| pki-coreRed Hat | Default status: unaffected | See vendor advisory |
| pki-coreRed Hat | Default status: unaffected | See vendor advisory |
| pki-core:10.6/pki-coreRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-80110
- https://access.redhat.com/errata/RHSA-2026:73765
- https://access.redhat.com/errata/RHSA-2026:73766
- https://access.redhat.com/errata/RHSA-2026:86621
- https://access.redhat.com/errata/RHSA-2026:86623
- https://access.redhat.com/security/cve/CVE-2026-80110
- https://bugzilla.redhat.com/show_bug.cgi?id=2523749