AWS security bulletins
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-20T20:23:23.199Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-195-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Path traversal in AWS MCP server affects AI agent deployments; file read/write capability requires immediate patching. |
| signals | path 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-20T20:23:19.924Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-194-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Identity sync privilege escalation affecting IAM Identity Center group memberships and permission assignments. |
| signals | identity 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
Issue with nginx HTTP/2 Implementation
Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-20T07:18:40.393Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-192-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | nginx is core infrastructure software in dependency trees. HTTP/2 layer bypass of WAF is actionable threat. |
| signals | nginx 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-20T07:18:35.080Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-191-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | AWS SDK for PHP encryption client vulnerability affecting S3 object decryption. Cryptographic weakness in authentication tag validation. |
| signals | AWS 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-20T07:18:32.126Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-193-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.95, needed 0.55 |
|---|---|
| triage reasoning | Ruby RCE in regex engine affects Rails/Sinatra apps; unauthenticated remote exploitation; common dependency. |
| signals | known 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
PHP Foundation Security Releases – November 19, 2026
Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-19T20:39:28.543Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-190-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | PHP runtime security release affecting multiple versions and core components that platform leads run. |
| signals | PHP 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue
Do:Remediation evidence unavailable; check exposure and consult the vendor bulletin.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-19T07:29:22.851Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-189-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | OpenJDK memory safety issue affects Java services most companies run; fix available. |
| signals | memory 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-18T20:35:18.924Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-188-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.72, needed 0.55 |
|---|---|
| triage reasoning | AutoGluon is a widely-used ML framework; arbitrary file write via MITM on plaintext HTTP is exploitable in real deployments. |
| signals | known 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-17T20:58:46.763Z |
|---|---|
| captured at | 2026-11-17T20:58:46.952Z |
| source | https://aws.amazon.com/security/security-bulletins/2026-187-aws/ |
| content SHA-256 | 08dd227a5bf3060cd40385e9d7d12f3035471a981112e264a0eae2c41a6a341c |
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.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Authorization bypass in Kubernetes credential issuer affects identity and certificate infrastructure; EKS add-on means AWS-managed component. |
| signals | Kubernetes 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |
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.
Show the reasoning — raw diff, triage verdict, confidence
+## 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.
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-11-17T20:58:43.720Z |
|---|---|
| captured at | unavailable |
| source | https://aws.amazon.com/security/security-bulletins/2026-186-aws/ |
| content SHA-256 | unavailable |
bulletin retrieval or evidence validation failed
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | EFS-utils is standard infrastructure software. TOCTOU race allows privilege escalation on shared hosts. |
| signals | known 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 model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |