cve.bz

CVE-2026-80110 Incorrect Authorization

8.1 highEPSS 0.2%Fix available

High (8.1). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat Enterprise Linux 10: fixed in 0:11.9.0-5.el10_2
  • Red Hat Red Hat Enterprise Linux 10.0 Extended Update Support: fixed in 0:11.6.0-3.el10_0.1
  • Red Hat Red Hat Enterprise Linux 9: fixed in 0:11.7.1-2.el9_8
  • Red Hat Red Hat Enterprise Linux 9.6 Extended Update Support: fixed in 0:11.6.0-4.el9_6
  • Red Hat, AlmaLinux, Rocky Linux: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-80110 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80110?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80110?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80110 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat Enterprise Linux 100:11.9.0-5.el10_2
Red Hat Enterprise Linux 10.0 Extended Update Support0:11.6.0-3.el10_0.1
Red Hat Enterprise Linux 90:11.7.1-2.el9_8
Red Hat Enterprise Linux 9.6 Extended Update Support0:11.6.0-4.el9_6

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTS and 1 moredogtag-pkino fix listedUBUNTU-CVE-2026-80110
Red Hatenterprise_linux:9::appstreampki-core, idm-pki-ca, idm-pki-kra and 8 more0:11.7.1-2.el9_8RHSA-2026:73766
Red Hatenterprise_linux:10.2dogtag-pki, idm-pki-ca, idm-pki-kra and 8 more0:11.9.0-5.el10_2RHSA-2026:73765
Red Hatenterprise_linux_eus:10.0dogtag-pki, idm-pki-ca, idm-pki-kra and 8 more0:11.6.0-3.el10_0.1RHSA-2026:86621
Red Hatrhel_eus:9.6::appstreampki-core, idm-pki-ca, idm-pki-kra and 8 more0:11.6.0-4.el9_6RHSA-2026:86623
AlmaLinux9idm-pki-ca, idm-pki-kra, idm-pki-acme and 5 more11.7.1-2.el9_8ALSA-2026:73766
AlmaLinux10idm-pki-ca, idm-pki-kra, idm-pki-acme and 4 more11.9.0-5.el10_2.alma.1ALSA-2026:73765
Rocky Linux9pki-core0:11.7.1-2.el9_8RLSA-2026:73766
Rocky Linux10dogtag-pki0:11.9.0-5.el10_2.rocky.0.1RLSA-2026:73765

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Rated Important: an authenticated Certificate Manager Agent -- a non-administrative role -- can author and activate an arbitrary certificate-issuance profile, an operation meant to require Administrator privilege. This directly compromises the integrity of the CA's issuance policy and poses a confidentiality risk to relying parties trusting the resulting certificates. Not Critical, since it requires an existing authenticated credential rather than unauthenticated remote code execution.

Red Hat's mitigation

There is no way to mitigate this issue other than applying an update once available. As a partial mitigation, limiting membership in the Certificate Manager Agents group to trusted users reduces exposure, since exploitation requires an authenticated credential in that role.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10dogtag-pki-0:11.9.0-5.el10_2Fixed 2026-09-30RHSA-2026:73765
Red Hat Enterprise Linux 10.0 Extended Update Supportdogtag-pki-0:11.6.0-3.el10_0.1Fixed 2026-10-21RHSA-2026:86621
Red Hat Enterprise Linux 9pki-core-0:11.7.1-2.el9_8Fixed 2026-09-30RHSA-2026:73766
Red Hat Enterprise Linux 9.6 Extended Update Supportpki-core-0:11.6.0-4.el9_6Fixed 2026-10-21RHSA-2026:86623
Red Hat Certificate System 9pki-coreNot affected
Red Hat Enterprise Linux 6pki-coreOut of support scope
Red Hat Enterprise Linux 7pki-coreNot affected
Red Hat Enterprise Linux 8pki-coreNot affected
Red Hat Enterprise Linux 8pki-core:10.6/pki-coreAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80110.

References

Check your stackJSON