AWS security bulletins

14 items in the render window (newest 100 + all corrections; not this source's all-time total) · status healthy · last successful fetch 2026-11-21 19:16 UTC
Feed for this sourceRSS
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-20 20:23 UTC

CVE-2026-130901 - Improper limitation of a pathname to a restricted directory in Amazon awslabs.document-loader-mcp-server

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-130901 - Improper limitation of a pathname to a restricted directory in Amazon awslabs.document-loader-mcp-server. Source event: 2026-11-20T18:45:40+00:00. RSS discovery: 2026-11-20T20:20:25.272321+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-130901. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-195-aws/ (retrieval attempted 2026-11-20T20:23:23.199Z; RSS discovery 2026-11-20T20:20:25.272321+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-130901 - Improper limitation of a pathname to a restricted directory in Amazon awslabs.document-loader-mcp-server
+https://aws.amazon.com/security/security-bulletins/rss/2026-195-aws/
+Fri, 20 Nov 2026 18:45:40 +0000
+
+Bulletin ID: 2026-195-AWS Publication Date: 11/20/2026 10:30 AM PST
+Description:
+Improper limitation of a pathname to a restricted directory in the file access checks in Amazon awslabs.document-loader-mcp-server 1.0.10 through 1.0.20 might allow a context-dependent actor, via crafted document content processed by an MCP client, to read files outside the intended base directory and, in 1.0.12 through 1.0.20, to write PNG slide images outside it. This occurs when DOCUMENT_BASE_DIR is not set or is empty and the CI, GITHUB_ACTIONS or PYTEST_CURRENT_TEST environment variable is present. Versions before 1.0.10 do not restrict file access to a base directory.
+Impacted versions: >= 1.0.10 AND < 1.0.21
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-20T20:23:23.199Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-195-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningPath traversal in AWS MCP server affects AI agent deployments; file read/write capability requires immediate patching.
signalspath traversal vulnerability in AWS-published tool · affects MCP (Model Context Protocol) server — AI agent framework · allows arbitrary file read and write when conditions met · specific affected versions identified (1.0.10–1.0.20) · fixed version available (1.0.21+) · context-dependent but exploitable via crafted document content
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-20 20:23 UTC

CVE-2026-133199 - Incorrect privilege assignment on reused e-mail addresses or group names in AWS ssosync

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-133199 - Incorrect privilege assignment on reused e-mail addresses or group names in AWS ssosync. Source event: 2026-11-20T16:41:29+00:00. RSS discovery: 2026-11-20T20:20:25.034556+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-133199. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-194-aws/ (retrieval attempted 2026-11-20T20:23:19.924Z; RSS discovery 2026-11-20T20:20:25.034556+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-133199 - Incorrect privilege assignment on reused e-mail addresses or group names in AWS ssosync
+https://aws.amazon.com/security/security-bulletins/rss/2026-194-aws/
+Fri, 20 Nov 2026 16:41:29 +0000
+
+Bulletin ID: 2026-194-AWS Publication Date: 11/20/2026 08:30 AM PST
+Description:
+Incorrect privilege assignment in the user and group reconciliation logic in AWS ssosync before 2.9.5 might allow an authenticated remote user who is assigned a reused Google Workspace e-mail address or group name to inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity, via automatic synchronization of that Google Workspace account or group.
+Impacted versions: < 2.9.5
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-20T20:23:19.924Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-194-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningIdentity sync privilege escalation affecting IAM Identity Center group memberships and permission assignments.
signalsidentity and SSO software (AWS ssosync) · privilege escalation via reused email/group names · authenticated remote user can inherit unrelated IAM permissions · affects cloud control plane identity layer · fixed version available (2.9.5) · known exploitation not stated but privilege inheritance is actionable
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-20 07:18 UTC

Issue with nginx HTTP/2 Implementation

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDIssue with nginx HTTP/2 Implementation. Source event: 2026-11-19T22:48:05+00:00. RSS discovery: 2026-11-20T07:16:32.297642+00:00.
WHY IT MATTERSThe captured feed identifies a vendor advisory. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-192-aws/ (retrieval attempted 2026-11-20T07:18:40.393Z; RSS discovery 2026-11-20T07:16:32.297642+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## Issue with nginx HTTP/2 Implementation
+https://aws.amazon.com/security/security-bulletins/rss/2026-192-aws/
+Thu, 19 Nov 2026 22:48:05 +0000
+
+Bulletin ID: 2026-192-AWS Publication Date: 11/19/2026 15:00 PM PST
+Description:
+AWS is aware of the nginx issues published on November 18, 2026 (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-113425, CVE-2026-121810 and CVE-2026-118899). These issues have been addressed in nginx version 1.30.7 (stable) and 1.31.9 (mainline). We recommend upgrading to the latest version. We are actively deploying mitigations worldwide to address these issues.
+Because these issues can be leveraged at the HTTP/2 protocol layer before a complete HTTP request is formed, AWS WAF managed and custom rules cannot effectively detect or block them.
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-20T07:18:40.393Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-192-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningnginx is core infrastructure software in dependency trees. HTTP/2 layer bypass of WAF is actionable threat.
signalsnginx vulnerabilities affecting HTTP/2 protocol layer · multiple CVEs (6 total) in widely-deployed web server · AWS WAF cannot mitigate at protocol layer · AWS actively deploying mitigations · fixed versions specified (1.30.7 stable, 1.31.9 mainline) · known to AWS and published by vendor
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-20 07:18 UTC

CVE-2026-132607 - GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-132607 - GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP. Source event: 2026-11-19T21:46:07+00:00. RSS discovery: 2026-11-20T07:16:32.13074+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-132607. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-191-aws/ (retrieval attempted 2026-11-20T07:18:35.080Z; RSS discovery 2026-11-20T07:16:32.13074+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-132607 - GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP
+https://aws.amazon.com/security/security-bulletins/rss/2026-191-aws/
+Thu, 19 Nov 2026 21:46:07 +0000
+
+Bulletin ID: 2026-191-AWS Publication Date: 11/19/2026 13:00 PM PST
+Description:
+We identified CVE-2026-132607, an issue in the decryption component of Amazon S3 Encryption Client for PHP in the AWS SDK for PHP. The client did not verify the length of the AES-GCM authentication tag recorded in an object's metadata. A user with read and write access to an encrypted object, who knows or can guess its plaintext, might craft a ciphertext that decrypts to plaintext of their choice of the same length. This requires repeated writes to the object. The issue does not disclose the plaintext or the encryption key.
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-20T07:18:35.080Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-191-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningAWS SDK for PHP encryption client vulnerability affecting S3 object decryption. Cryptographic weakness in authentication tag validation.
signalsAWS SDK for PHP — dependency tree package · encryption client vulnerability — cryptographic weakness · GCM authentication tag bypass — authentication downgrade · known CVE with assigned number · affects S3 encryption, a core managed service · plaintext substitution attack possible with write access
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-20 07:18 UTC

CVE-2026-132825 and related issues – Ruby regular expression engine and string case conversion

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-132825 and related issues – Ruby regular expression engine and string case conversion. Source event: 2026-11-19T23:06:34+00:00. RSS discovery: 2026-11-20T07:16:31.972884+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-132825. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-193-aws/ (retrieval attempted 2026-11-20T07:18:32.126Z; RSS discovery 2026-11-20T07:16:31.972884+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-132825 and related issues – Ruby regular expression engine and string case conversion
+https://aws.amazon.com/security/security-bulletins/rss/2026-193-aws/
+Thu, 19 Nov 2026 23:06:34 +0000
+
+Bulletin ID: 2026-193-AWS Publication Date: 11/19/2026 15:05 PM PST
+Description:
+On November 18, 2026, the Ruby maintainers published fixes for seven issues in CRuby's regular expression engine and string case conversion, including CVE-2026-132825. These issues affect Ruby versions before 4.0.10, 3.4.13, and 3.3.14 and could allow remote code execution in some configurations.
+These issues are memory-safety issues in Ruby's regular expression engine and in string case conversion on certain non-UTF-8 encodings. When an application processes third party-controlled input through these code paths, a remote, unauthenticated actor might be able to crash the process, read memory, or run arbitrary code. Applications built on Rack, including Rails and Sinatra, might be reachable through default request handling.
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-20T07:18:32.126Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-193-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.55
triage reasoningRuby RCE in regex engine affects Rails/Sinatra apps; unauthenticated remote exploitation; common dependency.
signalsknown exploitation pathway: Ruby regex engine and string case conversion · remote code execution possible · affects widely-used frameworks: Rails, Sinatra, Rack · unauthenticated remote attack · affects dependency tree: Ruby is a runtime; Rails/Sinatra are common service frameworks · multiple CVEs with published fixes available · specific affected versions listed: <4.0.10, <3.4.13, <3.3.14
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-19 20:39 UTC

PHP Foundation Security Releases – November 19, 2026

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDPHP Foundation Security Releases – November 19, 2026. Source event: 2026-11-19T18:30:09+00:00. RSS discovery: 2026-11-19T20:37:56.299454+00:00.
WHY IT MATTERSThe captured feed identifies a vendor advisory. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-190-aws/ (retrieval attempted 2026-11-19T20:39:28.543Z; RSS discovery 2026-11-19T20:37:56.299454+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## PHP Foundation Security Releases – November 19, 2026
+https://aws.amazon.com/security/security-bulletins/rss/2026-190-aws/
+Thu, 19 Nov 2026 18:30:09 +0000
+
+Bulletin ID: 2026-190-AWS Publication Date: 11/19/2026 10:00 AM PST
+Description:
+AWS is aware of security releases that the PHP Foundation published on November 19, 2026. PHP versions 8.2.36, 8.3.37, 8.4.28, and 8.5.13 address 17 issues across the PHP 8.2, 8.3, 8.4, and 8.5 branches. The issues are in the following components: - The PHP engine - PHP-FPM and the PHP CGI binary - The SOAP, Phar, session, DOM, and date extensions - The HTTP and FTP stream wrappers - The PHP 8.5 RFC 3986 URI implementation
+Patching the affected software remains the only complete fix and should be the first priority. We will update this bulletin as more information becomes available.
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-19T20:39:28.543Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-190-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningPHP runtime security release affecting multiple versions and core components that platform leads run.
signalsPHP runtime security release · multiple versions affected (8.2, 8.3, 8.4, 8.5) · 17 issues across core components · affects PHP-FPM, CGI, SOAP, Phar, session, DOM, date extensions · affects HTTP and FTP stream wrappers · PHP is in normal service dependency trees · patching recommended as first priority
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-19 07:29 UTC

CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue. Source event: 2026-11-19T03:02:28+00:00. RSS discovery: 2026-11-19T07:27:20.912958+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-114938. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-189-aws/ (retrieval attempted 2026-11-19T07:29:22.851Z; RSS discovery 2026-11-19T07:27:20.912958+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue
+https://aws.amazon.com/security/security-bulletins/rss/2026-189-aws/
+Thu, 19 Nov 2026 03:02:28 +0000
+
+Bulletin ID: 2026-189-AWS Publication Date: 11/18/2026 17:00 PM PST
+Description:
+AWS is aware of CVE-2026-114938, a memory issue in the Base64 decoder intrinsic of OpenJDK 17.0.6 and later on x86-64 processors that support AVX-512 VBMI. A fix is available in the November 2026 OpenJDK updates. AWS is working to deploy the fix to affected AWS services
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-19T07:29:22.851Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-189-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningOpenJDK memory safety issue affects Java services most companies run; fix available.
signalsmemory issue in widely-used runtime (OpenJDK) · out-of-bounds write — memory safety vulnerability · affects Java services in dependency tree · fix available and AWS deploying to control plane · specific CVE with publication date
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-18 20:35 UTC

CVE-2026-130638 - Path traversal in the object detection dataset preparation tool in AutoGluon MultiModal

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-130638 - Path traversal in the object detection dataset preparation tool in AutoGluon MultiModal. Source event: 2026-11-18T18:18:11+00:00. RSS discovery: 2026-11-18T20:31:42.573757+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-130638. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-188-aws/ (retrieval attempted 2026-11-18T20:35:18.924Z; RSS discovery 2026-11-18T20:31:42.573757+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-130638 - Path traversal in the object detection dataset preparation tool in AutoGluon MultiModal
+https://aws.amazon.com/security/security-bulletins/rss/2026-188-aws/
+Wed, 18 Nov 2026 18:18:11 +0000
+
+Bulletin ID: 2026-188-AWS Publication Date: 11/18/2026 10:00 AM PST
+Description:
+Relative path traversal in the object detection dataset preparation tool in AutoGluon Multimodal before 1.6.0 might allow adversary-in-the-middle attackers to write arbitrary files with the privileges of the user running the tool via a crafted dataset archive substituted for a dataset downloaded over plaintext HTTP.
+Impacted versions: < 1.6.0
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-18T20:35:18.924Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-188-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.72, needed 0.55
triage reasoningAutoGluon is a widely-used ML framework; arbitrary file write via MITM on plaintext HTTP is exploitable in real deployments.
signalsknown exploitation vector: adversary-in-the-middle + arbitrary file write · AutoGluon is ML/AI framework in dependency tree of data science teams · path traversal + privilege escalation chain · fixed version available (1.6.0) · plaintext HTTP download vulnerability
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-17 20:58 UTC

CVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

Do:Open the item for the complete captured vendor guidance and its conditions.
WHAT CHANGEDCVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer). Source event: 2026-11-17T20:11:26+00:00. RSS discovery: 2026-11-17T20:55:50.844034+00:00.
WHY IT MATTERSCurrent bulletin, captured 2026-11-17T20:58:46.952Z: AWS Private CA Connector for Kubernetes (aws-privateca-issuer) is an open-source controller, maintained by AWS and distributed as an Amazon EKS add-on, that issues certificates from AWS Private CA for cert-manager. We identified two issues in how the controller loads AWS credentials for a namespace-scoped issuer (AWSPCAIssuer). In both, a user with permission to create namespace-scoped issuers could obtain certificates, including subordinate CA certificates, that their own permissions do not authorize. CVE-2026-130622: a namespace-scoped issuer that references an AWS credentials Secret in a different namespace causes the controller to sign with that namespace's stored AWS credentials. This applies only where a namespace stores AWS access keys in a Kubernetes Secret. CVE-2026-130623: a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own AWS identity. Such an issuer can obtain certificates from every AWS Private CA and certificate template reachable by that identity or by any IAM role the identity can assume. This applies wherever the controller uses its own AWS identity (IRSA, EKS Pod Identity, EC2 Instance Role, or IAM Roles Anywhere) and tenants can create namespace-scoped issuers Impacted versions: aws-privateca-issuer before v1.12.0 AWS Private CA Connector for Kubernetes EKS add-on before v1.12.0-eksbuild.1
WHAT TO DOCurrent vendor guidance, captured 2026-11-17T20:58:46.952Z (separate from RSS discovery 2026-11-17T20:55:50.844034+00:00): Resolution [B1]: These issues have been addressed in aws-privateca-issuer version v1.12.0 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.12.0-eksbuild.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Resolution [B2]: Action required before upgrading: v1.12.0 rejects a cross-namespace secretRef and no longer lets a namespace-scoped issuer fall back to the controller's AWS identity, so issuers that rely on either will stop issuing after the upgrade. Before upgrading, record which issuers are affected. Then apply the v1.12.0 CRDs (EKS add-on users can apply them directly before updating the add-on) and migrate those issuers as follows. Resolution [B3]: For CVE-2026-130622, copy any credentials Secret you intend a namespace-scoped issuer to use into that issuer's namespace, and update the issuer's secretRef.namespace to match. Resolution [B4]: For CVE-2026-130623, give every namespace-scoped issuer that relies on the controller's AWS identity its own credentials, including an issuer that sets only a role. Use either a serviceAccountRef with IRSA or a same-namespace secretRef. A serviceAccountRef needs IRSA set up for the issuer's ServiceAccount, and the controller needs permission to create tokens for that ServiceAccount. To prevent outages, ensure both the controller's identity and the ServiceAccount are in the trust policy of each issuer's IAM role until the upgrade is complete. Remove the controller's entry after upgrading. Issuers using the controller's EKS Pod Identity credentials should move to IRSA since EKS Pod Identity cannot be assigned per issuer. Resolution [B5]: Setting the Helm chart or EKS add-on configuration value enableIssuerAmbientCredentials to true restores the fallback to the controller's AWS identity, but leaves the cluster exposed to CVE-2026-130623. Use it only where everyone who can create a namespace-scoped issuer is trusted. Resolution [B6]: To identify certificates that may have been issued incorrectly, review the issuers you recorded, your AWSPCAIssuer and CertificateRequest resources, and Kubernetes API audit logs (if enabled). CertificateRequest resources may have been deleted. Then generate an AWS Private CA audit report (CreateCertificateAuthorityAuditReport) or review AWS CloudTrail IssueCertificate events, retrieve each certificate by its ARN with GetCertificate, and compare it against the certificates expected in each cluster. Revoke any unexpected certificate with RevokeCertificate. Workarounds [B7]: If you cannot upgrade immediately, restrict permission to create or update AWSPCAIssuer resources to cluster administrators, and review any existing AWSPCAIssuers created by tenants. This will mitigate both issues until you can upgrade. If tenants must keep permission to create or update AWSPCAIssuer resources, there is no partial mitigation for CVE-2026-130622. You can reduce the risk of CVE-2026-130623 by scoping the controller's AWS identity to only the certificate authorities, templates and roles that every principal allowed to create issuers may use. Upgrading is the only complete remediation. Source for [B1], [B2], [B3], [B4], [B5], [B6], [B7]: https://aws.amazon.com/security/security-bulletins/2026-187-aws/
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
+https://aws.amazon.com/security/security-bulletins/rss/2026-187-aws/
+Tue, 17 Nov 2026 20:11:26 +0000
+
+Bulletin ID: 2026-187-AWS Publication Date: 11/17/2026 12:00 PM PST
+Description:
+Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes(aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.
+Impacted versions: - aws-privateca-issuer before v1.12.0 - AWS Private CA Connector for Kubernetes EKS add-on before v1.12.0-eksbuild.1
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · complete

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-17T20:58:46.763Z
captured at2026-11-17T20:58:46.952Z
sourcehttps://aws.amazon.com/security/security-bulletins/2026-187-aws/
content SHA-25608dd227a5bf3060cd40385e9d7d12f3035471a981112e264a0eae2c41a6a341c
CVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

Bulletin ID: 2026-187-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 11/17/2026 12:00 PM PST

Description:

AWS Private CA Connector for Kubernetes (aws-privateca-issuer) is an open-source controller, maintained by AWS and distributed as an Amazon EKS add-on, that issues certificates from AWS Private CA for cert-manager.

We identified two issues in how the controller loads AWS credentials for a namespace-scoped issuer (AWSPCAIssuer). In both, a user with permission to create namespace-scoped issuers could obtain certificates, including subordinate CA certificates, that their own permissions do not authorize.

CVE-2026-130622: a namespace-scoped issuer that references an AWS credentials Secret in a different namespace causes the controller to sign with that namespace's stored AWS credentials. This applies only where a namespace stores AWS access keys in a Kubernetes Secret.

CVE-2026-130623: a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own AWS identity. Such an issuer can obtain certificates from every AWS Private CA and certificate template reachable by that identity or by any IAM role the identity can assume. This applies wherever the controller uses its own AWS identity (IRSA, EKS Pod Identity, EC2 Instance Role, or IAM Roles Anywhere) and tenants can create namespace-scoped issuers

Impacted versions:

aws-privateca-issuer before v1.12.0

AWS Private CA Connector for Kubernetes EKS add-on before v1.12.0-eksbuild.1

Resolution:

These issues have been addressed in aws-privateca-issuer version v1.12.0 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.12.0-eksbuild.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Action required before upgrading: v1.12.0 rejects a cross-namespace secretRef and no longer lets a namespace-scoped issuer fall back to the controller's AWS identity, so issuers that rely on either will stop issuing after the upgrade. Before upgrading, record which issuers are affected. Then apply the v1.12.0 CRDs (EKS add-on users can apply them directly before updating the add-on) and migrate those issuers as follows.

For CVE-2026-130622, copy any credentials Secret you intend a namespace-scoped issuer to use into that issuer's namespace, and update the issuer's secretRef.namespace to match.

For CVE-2026-130623, give every namespace-scoped issuer that relies on the controller's AWS identity its own credentials, including an issuer that sets only a role. Use either a serviceAccountRef with IRSA or a same-namespace secretRef. A serviceAccountRef needs IRSA set up for the issuer's ServiceAccount, and the controller needs permission to create tokens for that ServiceAccount. To prevent outages, ensure both the controller's identity and the ServiceAccount are in the trust policy of each issuer's IAM role until the upgrade is complete. Remove the controller's entry after upgrading. Issuers using the controller's EKS Pod Identity credentials should move to IRSA since EKS Pod Identity cannot be assigned per issuer.

Setting the Helm chart or EKS add-on configuration value enableIssuerAmbientCredentials to true restores the fallback to the controller's AWS identity, but leaves the cluster exposed to CVE-2026-130623. Use it only where everyone who can create a namespace-scoped issuer is trusted.

To identify certificates that may have been issued incorrectly, review the issuers you recorded, your AWSPCAIssuer and CertificateRequest resources, and Kubernetes API audit logs (if enabled). CertificateRequest resources may have been deleted. Then generate an AWS Private CA audit report (CreateCertificateAuthorityAuditReport) or review AWS CloudTrail IssueCertificate events, retrieve each certificate by its ARN with GetCertificate, and compare it against the certificates expected in each cluster. Revoke any unexpected certificate with RevokeCertificate.

Workarounds:

If you cannot upgrade immediately, restrict permission to create or update AWSPCAIssuer resources to cluster administrators, and review any existing AWSPCAIssuers created by tenants. This will mitigate both issues until you can upgrade. If tenants must keep permission to create or update AWSPCAIssuer resources, there is no partial mitigation for CVE-2026-130622. You can reduce the risk of CVE-2026-130623 by scoping the controller's AWS identity to only the certificate authorities, templates and roles that every principal allowed to create issuers may use. Upgrading is the only complete remediation.

References:

CVE-2026-130622

CVE-2026-130623

GHSA-c68x-c9v2-p9hw

GHSA-vx84-39ff-mhjj

Please email aws-security@amazon.com with any s ecurity questions or concerns.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningAuthorization bypass in Kubernetes credential issuer affects identity and certificate infrastructure; EKS add-on means AWS-managed component.
signalsKubernetes security connector — developer tool in dependency tree · Authorization bypass in credential handling — authentication/identity impact · Affects AWS managed service (EKS add-on) — control plane adjacent · Cross-namespace privilege escalation — CA certificate theft possible · Fixed version available (v1.12.0) — actionable patch exists · Two CVEs, authentication required but low barrier (namespace-scoped permission)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
ACTION NEEDED SECURITY AWS security bulletins · 2026-11-17 20:58 UTC

CVE-2026-130621- Time-of-check time-of-use race condition in the port selection in AWS efs-utils

Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
WHAT CHANGEDCVE-2026-130621- Time-of-check time-of-use race condition in the port selection in AWS efs-utils. Source event: 2026-11-17T19:18:32+00:00. RSS discovery: 2026-11-17T20:55:50.70859+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-130621. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-186-aws/ (retrieval attempted 2026-11-17T20:58:43.720Z; RSS discovery 2026-11-17T20:55:50.70859+00:00).
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-130621- Time-of-check time-of-use race condition in the port selection in AWS efs-utils
+https://aws.amazon.com/security/security-bulletins/rss/2026-186-aws/
+Tue, 17 Nov 2026 19:18:32 +0000
+
+Bulletin ID: 2026-186-AWS Publication Date: 11/17/2026 11:00 AM PST
+Description:
+A time-of-check time-of-use (TOCTOU) race condition in the local port selection in AWS efs-utils (amazon-efs-utils) before 3.3.5 might allow a user that can start EFS mounts on a shared host to read and write a different Amazon EFS or S3 Files file system that is mounted on that same host, under that mount's IAM identity and access point, via concurrent mount operations. Only file systems mounted on the same host at the same time can be affected.
+Impacted versions: - amazon-efs-utils < v3.3.5 - aws-efs-csi-driver < v3.5.4
+Refer to the article for the most up-to-date and complete information.
SEPARATE BULLETIN CAPTURE · unavailable

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-11-17T20:58:43.720Z
captured atunavailable
sourcehttps://aws.amazon.com/security/security-bulletins/2026-186-aws/
content SHA-256unavailable
bulletin retrieval or evidence validation failed
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningEFS-utils is standard infrastructure software. TOCTOU race allows privilege escalation on shared hosts.
signalsknown vulnerability in widely-deployed AWS tooling · affects amazon-efs-utils and aws-efs-csi-driver — standard Kubernetes/EFS integration · privilege escalation: unprivileged user can access other filesystems under different IAM identity · fixed versions available (3.3.5 and 3.5.4) · race condition exploitable on shared hosts — common in multi-tenant Kubernetes clusters
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)
Corrections and arithmetic notes
CORRECTED FreeRTOS-Plus-TCP ≤V4.4.1 vulnerable to IPv6 RA spoofing and DNS cache poisoning
CORRECTED 2026-10-17 18:48 UTC — Correction, 17 October 2026: Our original advice omitted the fixed version and an additional configuration requirement for CVE-2026-102552. AWS’s current bulletin requires upgrading FreeRTOS-Plus-TCP to V4.4.2 and enabling ipconfigDNS_CHECK_REPLY_SOURCE_IP in FreeRTOSIPConfig.h. Source-IP checking is disabled by default, so upgrading alone does not remediate the DNS issue. Disabling IPv6 Router Advertisement processing is a workaround for CVE-2026-102551 only; it does not fix CVE-2026-102552. This clarification is based on the AWS bulletin retrieved on 17 October 2026. RADAR’s retained RSS capture lacked the remediation sections. We have not established whether the full AWS page contained these exact instructions when that RSS entry was captured.
AWS security bulletins · published 2026-10-17 04:29 UTC · corrected 2026-10-17 18:48 UTC · stood 14h 19m · cause writer overreach
WHAT CHANGED (CORRECTED)AWS disclosed CVE-2026-102551 and CVE-2026-102552 in FreeRTOS-Plus-TCP versions V4.4.1 and earlier on 16 October 2026. CVE-2026-102551 allows remote attackers to manipulate IPv6 gateway and routing configuration via spoofed Router Advertisements; the vulnerability is reachable in default configuration where ipconfigUSE_IPv6 and ipconfigUSE_RA are both enabled. CVE-2026-102552 allows remote attackers to poison the DNS cache by injecting replies from sources other than the queried server.
Original text (as first published, superseded)
WHAT TO DOInventory all embedded and IoT devices running FreeRTOS-Plus-TCP to identify those on V4.4.1 or earlier. Check AWS Security Bulletin 2026-139-AWS for patch availability and apply updates to affected devices. If immediate patching is not feasible, disable IPv6 RA processing by setting ipconfigUSE_RA to 0 as a temporary mitigation for CVE-2026-102551.
Full item and evidence ↗
CORRECTED Neptune deserialization flaw lets authenticated users trigger unsafe query processing
CORRECTED 2026-10-18 23:27 UTC — [CORRECTION · WHY IT MATTERS] Original: “This is a managed service vulnerability you cannot patch yourself — AWS must upgrade the engine.” Fact: The bulletin says the issue is fixed in Neptune engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0; clusters with auto minor version upgrade enabled get it in the next maintenance window, and customers who manage engine versions manually should upgrade. / Checked against AWS Security Bulletin 2026-136-AWS on 2026-10-18.
AWS security bulletins · published 2026-10-15 17:05 UTC · corrected 2026-10-18 23:27 UTC · stood 78h 22m · cause writer overreach
WHAT CHANGED (CORRECTED)AWS disclosed CVE-2026-110812 on 15 October 2026, a deserialization vulnerability in Apache TinkerPop's Gremlin functionality used by Amazon Neptune. All Neptune engine versions >=1.2.0.0 are affected. An authenticated principal with Neptune data-plane query permissions can submit requests that cause the query engine to process untrusted input unsafely, potentially leading to unintended activity within the query engine environment.
Original text (as first published, superseded)
WHY IT MATTERSThis is a managed service vulnerability you cannot patch yourself — AWS must upgrade the engine. An attacker who already has Neptune query permissions can exploit this to execute unintended operations in the query engine environment, which in a managed service context means activity outside your direct control. The broad version range means most production Neptune clusters are affected.
WHAT TO DOCheck your Neptune cluster engine versions in the AWS console. If running >=1.2.0.0, schedule an upgrade to the patched engine version listed in the full bulletin. Review IAM policies to confirm only necessary principals have neptune-db:* data-plane permissions, since exploitation requires authenticated query access.
TRIAGE SIGNALaffects cloud control plane / managed runtime that customer cannot patch
TRIAGE REASONINGManaged database service vulnerability requiring customer action; control plane component customers cannot patch themselves.
Full item and evidence ↗
CORRECTED AWS feed stopped carrying the text of security bulletin 2026-014 (RES); the bulletin was not withdrawn
CORRECTED 2026-09-24 22:33 UTC — Correction: AWS did not withdraw this bulletin. The bulletin page is still live and lists the same CVEs. AWS's feed stopped including the bulletin text on 24 Sep, and RADAR misread that as a removal. The rule that caused this is fixed.
AWS security bulletins · published 2026-09-24 19:12 UTC · corrected 2026-09-24 22:33 UTC · stood 3h 21m · cause source changed format
WHAT CHANGED (CORRECTED)AWS's security-bulletin feed stopped including the text of Security Bulletin 2026-014-AWS (published 6 April 2026) on 24 September 2026, and RADAR misread that as a removal. AWS did not withdraw the bulletin: the bulletin page is still live and lists the same CVEs, CVE-2026-5707, CVE-2026-5708 and CVE-2026-5709, affecting Research and Engineering Studio (RES) versions up to 2025.12.01.
Original text (as first published, superseded)
HEADLINEAWS withdrew security bulletin 2026-014 covering three RCE vulnerabilities in RES
WHAT CHANGEDAWS Security Bulletin 2026-014, published 6 April 2026, was removed from the feed on 24 September 2026. The bulletin documented CVE-2026-5707, CVE-2026-5708, and CVE-2026-5709 affecting Research and Engineering Studio (RES) versions through 2025.12.01. All three allowed remote code execution or privilege escalation: command injection via session names (CVE-5707), privilege escalation to instance profile permissions (CVE-5708), and command execution via FileBrowser API (CVE-5709). The entire advisory text, affected version ranges, and remediation guidance have been deleted.
WHY IT MATTERSIf you are running RES <= 2025.12.01, you no longer have an authoritative source documenting these vulnerabilities or how to fix them. The CVEs describe root-level command execution and AWS credential escalation paths that remain exploitable regardless of whether AWS has published guidance. Withdrawn advisories typically indicate either a retraction (the vulnerabilities were misreported) or a superseding update, but without replacement content you cannot distinguish between the two.
WHAT TO DOCheck the RES GitHub repository (aws/res) for issues or commits referencing CVE-2026-5707, CVE-2026-5708, or CVE-2026-5709 to determine whether patches were released and whether the withdrawal indicates a fix or a retraction. If you are running RES 2025.12.01 or earlier and find no clear retraction, treat the three CVEs as valid and either upgrade to a version past 2026.03 or disable virtual desktop session creation and FileBrowser functionality until you have confirmation.
Full item and evidence ↗
CORRECTED AWS feed stopped carrying the text of the QnABot CVE-2026-7191 bulletin; the bulletin was not withdrawn
CORRECTED 2026-09-24 22:33 UTC — Correction: AWS did not withdraw this bulletin. The bulletin page is still live and lists the same CVEs. AWS's feed stopped including the bulletin text on 24 Sep, and RADAR misread that as a removal. The rule that caused this is fixed.
AWS security bulletins · published 2026-09-24 19:12 UTC · corrected 2026-09-24 22:33 UTC · stood 3h 21m · cause source changed format
WHAT CHANGED (CORRECTED)AWS's security-bulletin feed stopped including the text of Security Bulletin 2026-020-AWS (published 27 April 2026) on 24 September 2026, and RADAR misread that as a removal. AWS did not withdraw the bulletin: it is still live and documents CVE-2026-7191, an arbitrary code execution issue for authenticated administrators in QnABot on AWS versions 7.2.4 and earlier.
Original text (as first published, superseded)
HEADLINEAWS removed CVE-2026-7191 QnABot security bulletin entirely
WHAT CHANGEDAWS Security Bulletin 2026-020-AWS, published 27 April 2026, was completely removed on 24 September 2026. The bulletin documented CVE-2026-7191, an arbitrary code execution vulnerability in QnABot on AWS versions ≤7.2.4 affecting authenticated administrators. All technical details including exploitation method, affected components (Lambda, OpenSearch, S3, DynamoDB), and version scope were deleted.
WHY IT MATTERSIf you are running QnABot ≤7.2.4 and acted on the original bulletin, you no longer have AWS's published guidance. If you did not act, you cannot now determine whether you are exposed or what to do. The removal provides no explanation—whether the CVE was withdrawn, the scope changed, or AWS is retracting the advisory.
WHAT TO DOCheck your QnABot version immediately. If ≤7.2.4, search CVE-2026-7191 in NIST NVD and vendor changelogs to determine current status. If you applied mitigations based on the original bulletin, verify they are still appropriate. Contact AWS Support for clarification if QnABot is in production.
Full item and evidence ↗