VulnerabilityPublished 29 Oct 2026

CVE-2026-119115: aws-privateca-issuer · Incorrect Authorization

Affects aws-privateca-issuerSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 1.10.1 soon.

Data as of 29 Oct 2026, 17:07 UTC

CVSS 3.1 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (AMZN)	CVSS 3.1	8.5
CNA (AMZN)	CVSS 4.0	8.4

Patch: Available – fixed in 1.10.1, 1.10.1-eksbuild.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade aws-privateca-issuer and cert-manager/aws-privateca-issuer to 1.10.1; aws-privateca-issuer to 1.10.1-eksbuild.1.

Affected software

Product	Affected	Fixed in
AWSaws-privateca-issuer	Affected <1.10.1	Fixed in 1.10.1
AWSaws-privateca-issuer	Affected <1.10.1-eksbuild.1	Fixed in 1.10.1-eksbuild.1
GitHubcert-manager/aws-privateca-issuer`pkg:github/cert-manager/aws-privateca-issuer`Other threats	Affected <1.10.1	Fixed in 1.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and users should upgrade aws-privateca-issuer to version 1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version 1.10.1-eksbuild.1. Additionally, users must update any certificate requests, Certificate resources, or Ingress annotations where issuerRef.kind is missing, incorrect, or does not match the referenced issuer. The issuerRef.kind must be exactly AWSPCAIssuer or AWSPCAClusterIssuer and must correspond to the referenced issuer. No other mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-119115 is an incorrect authorization vulnerability in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before version 1.10.1. It allows an authenticated remote user to obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize. The issue is fixed in version 1.10.1 and the corresponding EKS add-on version 1.10.1-eksbuild.1. Users must upgrade and ensure issuerRef.kind fields are correctly set to AWSPCAIssuer or AWSPCAClusterIssuer to match the referenced issuer.

Reports on CVE-2026-119115

CVE-2026-119115: AWS Private CA Connector · Incorrect Authorization in Issuer ResolutionAWS Security Bulletins2026-10-29

Impact

An authenticated remote user with limited privileges could obtain certificates, including subordinate CA certificates, that their approval policy does not authorize. This could lead to unauthorized issuance of certificates, potentially undermining trust and security within the Kubernetes cluster environment. The CVSS 3.1 base score is 8.5 (High), reflecting network attack vector, low complexity, low privileges required, no user interaction, scope change, low confidentiality impact, high integrity impact, and no availability impact.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

Reports on CVE-2026-119115

AI analysisMachine-generated, updated 29 Oct 2026, 16:53 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats