<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — verify_exposure</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/action/verify-exposure.xml" rel="self" type="application/rss+xml"/>
    <description>Items whose recommended action is verify_exposure.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>Budibase allows unauthenticated global-admin creation via init guard bypass</title>
      <link>https://radar.trulysovereign.com/items/e2c9fbb6-b972-4a0d-82a9-c86713ba70fa</link>
      <guid isPermaLink="false">e2c9fbb6-b972-4a0d-82a9-c86713ba70fa</guid>
      <pubDate>Sat, 21 Nov 2026 19:18:55 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-122247 published 20 November 2026 documents an unauthenticated vulnerability in @budibase/server that allows creation of global-admin accounts and databases by bypassing the one-time initialization guard on POST /api/global/users/init through tenant confusion. GitHub rates this high severity. No patched version is listed in the advisory.

Why it matters: An unauthenticated attacker can create admin accounts with full privileges, bypassing the intended one-time setup restriction. This grants complete control over the Budibase instance and its databases without any prior access.

What to do: Check whether you run @budibase/server in production. If so, verify whether the /api/global/users/init endpoint is exposed and whether unauthorized admin accounts exist. Remediation: see bulletin https://github.com/advisories/GHSA-25qc-m4pw-2w8r</description>
    </item>
    <item>
      <title>CVE-2026-130901 - Improper limitation of a pathname to a restricted directory in Amazon awslabs.document-loader-mcp-server</title>
      <link>https://radar.trulysovereign.com/items/b1257665-0c35-4824-bef9-273d4d712557</link>
      <guid isPermaLink="false">b1257665-0c35-4824-bef9-273d4d712557</guid>
      <pubDate>Fri, 20 Nov 2026 20:23:23 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-195-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-130901. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CVE-2026-133199 - Incorrect privilege assignment on reused e-mail addresses or group names in AWS ssosync</title>
      <link>https://radar.trulysovereign.com/items/ba896638-0051-45f7-9c32-3f47e556b5c7</link>
      <guid isPermaLink="false">ba896638-0051-45f7-9c32-3f47e556b5c7</guid>
      <pubDate>Fri, 20 Nov 2026 20:23:20 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-194-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-133199. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CISA adds Apache Roller deserialization flaw to KEV catalog</title>
      <link>https://radar.trulysovereign.com/items/dd538b14-fc29-4800-8b8c-8eaf3b1f677b</link>
      <guid isPermaLink="false">dd538b14-fc29-4800-8b8c-8eaf3b1f677b</guid>
      <pubDate>Fri, 20 Nov 2026 20:21:50 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json">CISA Known Exploited Vulnerabilities</source>
      <description>CISA added CVE-2026-129448 to the Known Exploited Vulnerabilities catalog on 2026-11-20. The vulnerability is a deserialization of untrusted data flaw in Apache Roller. Due date for federal agencies is 2026-11-23.

Why it matters: Deserialization vulnerabilities allow attackers to execute arbitrary code by sending crafted data to the application. CISA's KEV listing indicates active exploitation in the wild.

What to do: Check whether you run Apache Roller in any environment. If yes, apply mitigations per Apache's vendor instructions by 2026-11-23 or discontinue use if mitigations are unavailable.</description>
    </item>
    <item>
      <title>CISA adds SAP NetWeaver query logic vulnerability to KEV catalog</title>
      <link>https://radar.trulysovereign.com/items/a9703222-7c79-49b7-8a20-df358ce6432c</link>
      <guid isPermaLink="false">a9703222-7c79-49b7-8a20-df358ce6432c</guid>
      <pubDate>Fri, 20 Nov 2026 20:21:33 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json">CISA Known Exploited Vulnerabilities</source>
      <description>CISA added CVE-2025-42884 to the Known Exploited Vulnerabilities catalog on 2026-11-20. The vulnerability is an improper neutralization of special elements in data query logic in SAP NetWeaver. Due date for federal agencies is 2026-11-23.

Why it matters: Active exploitation is confirmed. SAP NetWeaver is widely deployed enterprise application server software, and query logic vulnerabilities typically allow unauthorized data access or manipulation.

What to do: Verify exposure: check if you run SAP NetWeaver and whether the affected component is internet-facing. Remediation: see bulletin https://www.cisa.gov/known-exploited-vulnerabilities-catalog</description>
    </item>
    <item>
      <title>Issue with nginx HTTP/2 Implementation</title>
      <link>https://radar.trulysovereign.com/items/42024c29-b2c8-43f3-bdd8-90dda628b637</link>
      <guid isPermaLink="false">42024c29-b2c8-43f3-bdd8-90dda628b637</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:40 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-192-aws/">AWS security bulletins</source>
      <description>Issue 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 matters: The captured feed identifies a vendor advisory. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CVE-2026-132607 - GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP</title>
      <link>https://radar.trulysovereign.com/items/829bde5b-d009-4a1a-b498-502d3db76cd3</link>
      <guid isPermaLink="false">829bde5b-d009-4a1a-b498-502d3db76cd3</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:35 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-191-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-132607. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CVE-2026-132825 and related issues – Ruby regular expression engine and string case conversion</title>
      <link>https://radar.trulysovereign.com/items/35d616c1-c802-445a-949c-28b005dd6964</link>
      <guid isPermaLink="false">35d616c1-c802-445a-949c-28b005dd6964</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:32 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-193-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-132825. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>nginx HTTP/2 RCE vulnerabilities affect Apigee Edge for Private Cloud non-default configs</title>
      <link>https://radar.trulysovereign.com/items/e3c0b8e9-6a29-40ef-86aa-988e9a77fb5f</link>
      <guid isPermaLink="false">e3c0b8e9-6a29-40ef-86aa-988e9a77fb5f</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:18 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-087">Google Cloud security bulletins</source>
      <description>CVE-2026-123633 and CVE-2026-123007 were published on 2026-11-19, affecting nginx HTTP/2 module versions before 1.30.7. Apigee Edge for Private Cloud versions 4.54.00 and 4.53.01 use an affected nginx version. Default configurations are not vulnerable because HTTP/2 is not supported on Router virtual hosts, but non-default deployments that enable HTTP/2 are exposed to remote unauthenticated code execution.

Why it matters: A remote attacker can execute code on Apigee Routers configured to accept HTTP/2 connections without authentication. Default installations are safe, but any Router with HTTP/2 explicitly enabled on a virtual host is exploitable.

What to do: Check Router virtual host configurations for HTTP/2 enablement. If running default configuration, no action required. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-087.</description>
    </item>
    <item>
      <title>VMware vCenter and Cloud Foundation vulnerability affects Google Cloud VMware Engine</title>
      <link>https://radar.trulysovereign.com/items/dd1239c5-1629-45b3-aaa2-2b2f8b713d9b</link>
      <guid isPermaLink="false">dd1239c5-1629-45b3-aaa2-2b2f8b713d9b</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:06 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-085">Google Cloud security bulletins</source>
      <description>Google Cloud published security bulletin GCP-2026-085 on 2026-11-19, referencing VMware security advisory VMSA-2026-0009. The advisory identifies CVE-2026-123890, a critical severity vulnerability in VMware vCenter and VMware Cloud Foundation with no known workarounds.

Why it matters: Google Cloud VMware Engine and VMware solution on Google Cloud are managed services running the affected VMware components. Customers cannot patch these managed runtimes directly and must rely on Google Cloud to apply remediation.

What to do: Check the Google Cloud VMware Engine security bulletin and VMware solution on Google Cloud security bulletin linked in GCP-2026-085 for remediation status and any required customer actions. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-085</description>
    </item>
    <item>
      <title>PHP Foundation Security Releases – November 19, 2026</title>
      <link>https://radar.trulysovereign.com/items/8a13a163-2079-4033-83fc-65581abb51f3</link>
      <guid isPermaLink="false">8a13a163-2079-4033-83fc-65581abb51f3</guid>
      <pubDate>Thu, 19 Nov 2026 20:39:28 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-190-aws/">AWS security bulletins</source>
      <description>PHP 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 matters: The captured feed identifies a vendor advisory. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue</title>
      <link>https://radar.trulysovereign.com/items/403eeb82-2fe7-4b9e-a66d-3441e4b999ff</link>
      <guid isPermaLink="false">403eeb82-2fe7-4b9e-a66d-3441e4b999ff</guid>
      <pubDate>Thu, 19 Nov 2026 07:29:23 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-189-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-114938. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CVE-2026-130638 - Path traversal in the object detection dataset preparation tool in AutoGluon MultiModal</title>
      <link>https://radar.trulysovereign.com/items/d74bd8b2-768b-488a-97f1-ffd2e96ad9a2</link>
      <guid isPermaLink="false">d74bd8b2-768b-488a-97f1-ffd2e96ad9a2</guid>
      <pubDate>Wed, 18 Nov 2026 20:35:19 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-188-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-130638. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>CISA adds Apache Axis unsafe reflection vulnerability to KEV catalog</title>
      <link>https://radar.trulysovereign.com/items/57601b61-b131-4a28-8ab0-508507190b90</link>
      <guid isPermaLink="false">57601b61-b131-4a28-8ab0-508507190b90</guid>
      <pubDate>Wed, 18 Nov 2026 20:34:02 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json">CISA Known Exploited Vulnerabilities</source>
      <description>CISA added CVE-2026-90436 to the Known Exploited Vulnerabilities catalog on 2026-11-18. The vulnerability is an unsafe reflection issue in Apache Axis, a server-side web services framework. The due date for required action is 2026-11-21.

Why it matters: Unsafe reflection vulnerabilities in server-side frameworks are remote code execution class. CISA KEV listing means active exploitation has been observed in the wild. Federal agencies and BOD 26-04 stakeholders must act by the due date.

What to do: Verify whether Apache Axis is in your dependency tree and what version you are running. Apply mitigations per vendor instructions by 2026-11-21, or discontinue use if mitigations are unavailable. Remediation: see bulletin https://www.cisa.gov/known-exploited-vulnerabilities-catalog</description>
    </item>
    <item>
      <title>CISA adds LiteLLM CVE-2026-40217 to KEV catalog</title>
      <link>https://radar.trulysovereign.com/items/ee552dc9-ae2d-4ebf-bf8b-8fa55e8ea1ac</link>
      <guid isPermaLink="false">ee552dc9-ae2d-4ebf-bf8b-8fa55e8ea1ac</guid>
      <pubDate>Wed, 18 Nov 2026 20:33:53 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json">CISA Known Exploited Vulnerabilities</source>
      <description>CISA added CVE-2026-40217 affecting BerriAI LiteLLM to the Known Exploited Vulnerabilities catalog on 2026-11-18. The vulnerability is classified as an unprotected alternate channel vulnerability. Due date for action is 2026-12-02.

Why it matters: Active exploitation is confirmed. Federal agencies are required to act by 2026-12-02 under BOD 26-04, and the KEV listing signals that this vulnerability is being used in the wild against real targets.

What to do: Check whether you run LiteLLM in any service. If yes, apply vendor mitigations by 2026-12-02 or discontinue use if mitigations are unavailable. Remediation: see bulletin https://www.cisa.gov/known-exploited-vulnerabilities-catalog</description>
    </item>
    <item>
      <title>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)</title>
      <link>https://radar.trulysovereign.com/items/153521b9-e63b-428f-a934-4df4bc5ef49c</link>
      <guid isPermaLink="false">153521b9-e63b-428f-a934-4df4bc5ef49c</guid>
      <pubDate>Tue, 17 Nov 2026 20:58:47 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-187-aws/">AWS security bulletins</source>
      <description>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). Source event: 2026-11-17T20:11:26+00:00. RSS discovery: 2026-11-17T20:55:50.844034+00:00.

Why it matters: Current 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 do: Current 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/</description>
    </item>
    <item>
      <title>CVE-2026-130621- Time-of-check time-of-use race condition in the port selection in AWS efs-utils</title>
      <link>https://radar.trulysovereign.com/items/e76c0145-a218-47c2-91db-c6f3d436018b</link>
      <guid isPermaLink="false">e76c0145-a218-47c2-91db-c6f3d436018b</guid>
      <pubDate>Tue, 17 Nov 2026 20:58:44 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://aws.amazon.com/security/security-bulletins/2026-186-aws/">AWS security bulletins</source>
      <description>CVE-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 matters: The captured feed identifies CVE-2026-130621. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.

What to do: Check 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).</description>
    </item>
    <item>
      <title>[CORRECTED] FreeRTOS-Plus-TCP ≤V4.4.1 vulnerable to IPv6 RA spoofing and DNS cache poisoning</title>
      <link>https://radar.trulysovereign.com/items/c2583dc0-a3e4-4f87-805e-ec2c2f13fa11</link>
      <guid isPermaLink="false">c2583dc0-a3e4-4f87-805e-ec2c2f13fa11</guid>
      <pubDate>Sat, 17 Oct 2026 04:29:21 GMT</pubDate>
      <category>verify_exposure</category>
      <category>corrected</category>
      <source url="https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/">AWS security bulletins</source>
      <description>[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.

Why it matters: Both vulnerabilities enable traffic interception and redirection on embedded and IoT devices running FreeRTOS-Plus-TCP. The IPv6 issue is exploitable in default configuration without requiring local network access. Devices using this stack for AWS IoT connectivity or edge services are exposed to man-in-the-middle attacks that can redirect traffic to attacker-controlled infrastructure.

What to do: Inventory embedded and IoT devices running FreeRTOS-Plus-TCP V4.4.1 or earlier. Upgrade them to V4.4.2 and enable ipconfigDNS_CHECK_REPLY_SOURCE_IP in FreeRTOSIPConfig.h: source-IP checking is disabled by default, so upgrading alone does not fix CVE-2026-102552. If you cannot upgrade immediately, setting ipconfigUSE_RA to 0 is a workaround for CVE-2026-102551 only; it does not address CVE-2026-102552. See AWS Security Bulletin 2026-139-AWS for the current guidance.

Original text (as first published, superseded):

WHAT TO DO: Inventory 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.</description>
    </item>
    <item>
      <title>[CORRECTED] Application Integration privilege escalation patched August 27</title>
      <link>https://radar.trulysovereign.com/items/2fc4875b-00de-47c3-b58e-883d213e40eb</link>
      <guid isPermaLink="false">2fc4875b-00de-47c3-b58e-883d213e40eb</guid>
      <pubDate>Wed, 14 Oct 2026 17:13:41 GMT</pubDate>
      <category>verify_exposure</category>
      <category>corrected</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-068">Google Cloud security bulletins</source>
      <description>[CORRECTED] Google patched CVE-2026-85298 in Application Integration on August 27, 2026. The vulnerability allowed authenticated users to escalate privileges and impersonate service accounts through incorrect authorization in AuthConfig validation and integration execution runtime.

Why it matters: Before Google's August 27, 2026 fix, an authenticated user could escalate privileges and impersonate a service account in a Google Cloud project using Application Integration. Google rates the issue Critical and has already patched it; Google states no customer action is required.

What to do: No customer action is required: Google patched CVE-2026-85298 on August 27, 2026. Optional, RADAR's suggestion rather than a Google requirement: if you have a specific concern about past service account misuse, review the relevant Cloud Audit Logs under your own security procedures.

Original text (as first published, superseded):

WHY IT MATTERS: An authenticated attacker could have gained service account credentials in your Google Cloud project, bypassing intended access controls. Google rates this critical severity.

WHAT TO DO: Verify that no unauthorized service account activity occurred between your first use of Application Integration and August 27, 2026. Review Cloud Audit Logs for unexpected impersonation events or privilege escalations in projects using Application Integration.</description>
    </item>
    <item>
      <title>[CORRECTED] AWS feed stopped carrying the text of security bulletin 2026-014 (RES); the bulletin was not withdrawn</title>
      <link>https://radar.trulysovereign.com/items/6f99c484-f40d-4dbe-aff2-44a56b13179a</link>
      <guid isPermaLink="false">6f99c484-f40d-4dbe-aff2-44a56b13179a</guid>
      <pubDate>Thu, 24 Sep 2026 19:12:53 GMT</pubDate>
      <category>verify_exposure</category>
      <category>corrected</category>
      <source url="https://aws.amazon.com/security/security-bulletins/rss/2026-014-aws/">AWS security bulletins</source>
      <description>[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.

Why it matters: Nothing was retracted. If you run an affected RES version, the bulletin's three vulnerabilities and its guidance still apply.

What to do: If you run Research and Engineering Studio, check your version against the live AWS Security Bulletin 2026-014-AWS and upgrade to RES 2026.03 or later, as the bulletin directs.

Original text (as first published, superseded):

HEADLINE: AWS withdrew security bulletin 2026-014 covering three RCE vulnerabilities in RES

WHAT CHANGED: AWS 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 MATTERS: If you are running RES &lt;= 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 DO: Check 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.</description>
    </item>
    <item>
      <title>[CORRECTED] AWS feed stopped carrying the text of the QnABot CVE-2026-7191 bulletin; the bulletin was not withdrawn</title>
      <link>https://radar.trulysovereign.com/items/ccfacdbd-790c-445d-99e5-1f00377f5dcc</link>
      <guid isPermaLink="false">ccfacdbd-790c-445d-99e5-1f00377f5dcc</guid>
      <pubDate>Thu, 24 Sep 2026 19:12:34 GMT</pubDate>
      <category>verify_exposure</category>
      <category>corrected</category>
      <source url="https://aws.amazon.com/security/security-bulletins/rss/2026-020-aws/">AWS security bulletins</source>
      <description>[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.

Why it matters: Nothing was retracted. QnABot on AWS 7.2.4 and earlier remains affected, and AWS states there is no workaround.

What to do: Check your QnABot on AWS version. If it is 7.2.4 or earlier, upgrade to 7.3.0 or later, as the live bulletin directs.

Original text (as first published, superseded):

HEADLINE: AWS removed CVE-2026-7191 QnABot security bulletin entirely

WHAT CHANGED: AWS 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 MATTERS: If 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 DO: Check 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.</description>
    </item>
  </channel>
</rss>
