CVE-2026-17039Low· 3.1▾ SunlitA 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 cer…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 17.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.3%
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.
redhat-pki (all versions)redhat-pki (all versions)pki-core (all versions)dogtag-pki (all versions)pki-core (all versions)pki-core (all versions)pki-core (all versions)pki-core (all versions)Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Deployments that do not configure a realm-mapped authorization manager (AuthzRealmDefault with a non-default realm-to-authorization-manager mapping) for multi-tenant or delegated sub-CA use are not exposed to this issue. For deployments that do use realm-based authorization, using a renewal profile that additionally restricts renewal requests to the original requester narrows exposure: the shipped caDirUserRenewal.cfg profile configures authz.acl=user_origreq="auth_token.uid", which independently blocks cross-user renewal by comparing the renewing caller's UID against the UID that submitted the original request. This is a partial mitigation only -- it is realm-blind rather than realm-aware, so a UID collision across two independently-administered realms' user directories would still bypass it -- and it does not apply to caManualRenewal.cfg or other shipped renewal profiles that configure no authz.acl, which remain exploitable as described. No complete mitigation is available; apply the update once released.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-2698High· 8.8Freeipa: delegation rules allow a proxy service to impersonate any user to access another target service
CVE-2026-121837Medium· 4.3Quarkus-rest-data-panache: quarkus-rest-data-panache: getter-level @securefield ignored for filter and sort
CVE-2024-10295High· 7.5Gateway: apicast basic auth bypass via malformed base64 headerssending non-base64 'basic' auth with special characters causes apicast to incorrectly authenticate a request
CVE-2026-118952Medium· 6.5Kroxylicious-authorizer-acl: kroxylicious: acl prefix matching can bypass authorization rules
CVE-2024-9902Medium· 6.3Ansible-core: ansible-core user may read/write unauthorized content
CVE-2024-10306Medium· 5.4A vulnerability was found in mod_proxy_cluster