{
  "schema_version": 1.1,
  "generated_at": "2026-10-17T04:30:36.075Z",
  "channel": "security_advisory",
  "channel_label": "Security Advisory Triage",
  "public": true,
  "count": 37,
  "contract": "https://radar.trulysovereign.com/docs/feed",
  "items": [
    {
      "id": "c2583dc0-a3e4-4f87-805e-ec2c2f13fa11",
      "channel": "security_advisory",
      "headline": "FreeRTOS-Plus-TCP ≤V4.4.1 vulnerable to IPv6 RA spoofing and DNS cache poisoning",
      "what_changed": "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_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 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.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/",
      "published_at": "2026-10-17T04:29:21.544777+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/c2583dc0-a3e4-4f87-805e-ec2c2f13fa11",
      "affects": [
        {
          "id": "cve-2026-102551",
          "type": "cve",
          "label": "CVE-2026-102551"
        },
        {
          "id": "cve-2026-102552",
          "type": "cve",
          "label": "CVE-2026-102552"
        },
        {
          "id": "freertos-plus-tcp",
          "type": "package",
          "label": "FreeRTOS-Plus-TCP",
          "unmapped": true
        },
        {
          "id": "aws",
          "type": "provider",
          "label": "aws"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "b22c4c5b-643b-4da1-82f9-6f1897a0dbc9",
      "channel": "security_advisory",
      "headline": "BeyondTrust Remote Support authentication bypass added to CISA KEV",
      "what_changed": "CISA added CVE-2026-102764 to the Known Exploited Vulnerabilities catalog on 16 October 2026. The vulnerability is an authentication bypass by spoofing in BeyondTrust Remote Support. Due date for federal agencies is 19 October 2026.",
      "why_matters": "This is remote access software with active exploitation and a three-day compliance window. An authentication bypass in this category means an attacker can gain the access your support staff has — to endpoints, to sessions, to whatever Remote Support reaches. If you run this product and it is internet-facing, you are in the window where exploitation is documented and the fix or mitigation must be live.",
      "what_to_do": "Check whether you run BeyondTrust Remote Support in any environment. If yes, apply the vendor's published mitigations immediately — CISA's required action references vendor instructions, so those exist. If the product is cloud-hosted, confirm the vendor has applied the mitigation. If you cannot mitigate by 19 October, take the service offline.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-16T21:12:09.3678+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/b22c4c5b-643b-4da1-82f9-6f1897a0dbc9",
      "affects": [
        {
          "id": "cve-2026-102764",
          "type": "cve",
          "label": "CVE-2026-102764"
        },
        {
          "id": "beyondtrust-remote-support",
          "type": "product",
          "label": "BeyondTrust Remote Support",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-19",
      "time_to_correct": null
    },
    {
      "id": "f36ee513-573a-4769-9960-c3e1b8720a3d",
      "channel": "security_advisory",
      "headline": "Fortinet path traversal vulnerability added to CISA KEV, patch due 19 October",
      "what_changed": "CISA added CVE-2025-61624 to the Known Exploited Vulnerabilities catalog on 16 October 2026. The vulnerability is a path traversal flaw affecting multiple Fortinet products. Federal agencies must apply mitigations by 19 October 2026 under BOD 26-04.",
      "why_matters": "Path traversal vulnerabilities allow attackers to access files outside intended directories, potentially exposing configuration files, credentials, or sensitive data. CISA only adds vulnerabilities to the KEV when active exploitation is confirmed in the wild. If you run affected Fortinet products with internet exposure, you are a target right now.",
      "what_to_do": "Check your Fortinet product inventory against the vendor advisory for CVE-2025-61624. If you are running an affected version, apply the vendor's mitigation instructions before 19 October. If no mitigation is available for your version, follow BOD 26-04 guidance to discontinue use or isolate the system from the internet.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-16T21:11:57.205611+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/f36ee513-573a-4769-9960-c3e1b8720a3d",
      "affects": [
        {
          "id": "cve-2025-61624",
          "type": "cve",
          "label": "CVE-2025-61624"
        },
        {
          "id": "fortinet",
          "type": "provider",
          "label": "fortinet",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-19",
      "time_to_correct": null
    },
    {
      "id": "1e224e4d-d714-453d-8691-9ae0141da8d7",
      "channel": "security_advisory",
      "headline": "Claude Code plugin hash pinning bypass patched in 2.1.179",
      "what_changed": "CVE-2026-86063 published 15 October 2026 for @anthropic-ai/claude-code. A high-severity vulnerability allows bypass of hash pinning, a cryptographic integrity control. First patched version is 2.1.179.",
      "why_matters": "Hash pinning prevents tampered or substituted plugins from executing. A bypass means an attacker who can position a malicious plugin can defeat the integrity check that would normally block it. Any deployment running an unpatched version accepts plugins it should reject.",
      "what_to_do": "Upgrade @anthropic-ai/claude-code to 2.1.179 or later. Grep package.json and lock files for the package name to confirm you are exposed before scheduling the update.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — npm",
      "source_url": "https://api.github.com/advisories?ecosystem=npm&severity=high&per_page=100",
      "published_at": "2026-10-16T04:42:16.92121+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/1e224e4d-d714-453d-8691-9ae0141da8d7",
      "affects": [
        {
          "id": "npm@anthropic-ai/claude-code",
          "type": "package",
          "label": "npm:@anthropic-ai/claude-code",
          "unmapped": true
        },
        {
          "id": "cve-2026-86063",
          "type": "cve",
          "label": "CVE-2026-86063"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "2f2b6fbd-b1fd-40d4-8541-8be6ee55bc98",
      "channel": "security_advisory",
      "headline": "OpenNext Cloudflare cache bypass allows middleware evasion via encoded paths",
      "what_changed": "GitHub published CVE-2026-100409 on 15 October 2026, a high-severity advisory for @opennextjs/cloudflare. The vulnerability allows cache interception to bypass middleware protection when paths are encoded. Version 1.20.2 patches the issue.",
      "why_matters": "If you run Next.js on Cloudflare with OpenNext and rely on middleware for authentication or authorization, an attacker can bypass those checks by encoding request paths. Protected routes become accessible without passing through your middleware layer.",
      "what_to_do": "Check your package.json or lock file for @opennextjs/cloudflare. If present and below 1.20.2, update to 1.20.2 or later. If you cannot update immediately, review your middleware logic and consider adding path normalization before authorization checks.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — npm",
      "source_url": "https://api.github.com/advisories?ecosystem=npm&severity=high&per_page=100",
      "published_at": "2026-10-16T04:42:06.351266+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/2f2b6fbd-b1fd-40d4-8541-8be6ee55bc98",
      "affects": [
        {
          "id": "npm@opennextjs/cloudflare",
          "type": "package",
          "label": "npm:@opennextjs/cloudflare",
          "unmapped": true
        },
        {
          "id": "cve-2026-100409",
          "type": "cve",
          "label": "CVE-2026-100409"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "93b372cc-d9e8-4ad9-8ce3-d5512034a886",
      "channel": "security_advisory",
      "headline": "CISA adds Atlassian CVE-2026-21589 to KEV catalog, due 2026-10-18",
      "what_changed": "CVE-2026-21589 was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-15. The vulnerability affects multiple Atlassian products and is classified as \"Files or Directories Accessible to External Parties.\" Federal agencies must act by 2026-10-18 under BOD 26-04.",
      "why_matters": "Active exploitation is confirmed — that is the threshold for KEV inclusion. If you run Atlassian products (Jira, Confluence, Bitbucket, Bamboo), an attacker can access files or directories that should be restricted. The three-day window indicates CISA considers this urgent.",
      "what_to_do": "Check your Atlassian product inventory against the vendor advisory for CVE-2026-21589. Apply the vendor's mitigation instructions before 2026-10-18 if you are a federal agency or contractor; apply them this week regardless. If no mitigation exists for your version, follow BOD 26-04 guidance to discontinue use or isolate the instance.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-15T21:26:59.413147+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/93b372cc-d9e8-4ad9-8ce3-d5512034a886",
      "affects": [
        {
          "id": "cve-2026-21589",
          "type": "cve",
          "label": "CVE-2026-21589"
        },
        {
          "id": "atlassian",
          "type": "provider",
          "label": "atlassian",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-18",
      "time_to_correct": null
    },
    {
      "id": "826a54ad-f6b8-4d18-8dde-5e0b8053ae57",
      "channel": "security_advisory",
      "headline": "Neptune deserialization flaw lets authenticated users trigger unsafe query processing",
      "what_changed": "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.",
      "why_matters": "This 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_do": "Check 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.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-136-aws/",
      "published_at": "2026-10-15T17:05:00.896946+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/826a54ad-f6b8-4d18-8dde-5e0b8053ae57",
      "affects": [
        {
          "id": "amazon-neptune",
          "type": "product",
          "label": "amazon neptune",
          "unmapped": true
        },
        {
          "id": "cve-2026-110812",
          "type": "cve",
          "label": "CVE-2026-110812"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "5d6e6508-2ab6-430a-b535-bfb220e028d4",
      "channel": "security_advisory",
      "headline": "AWS S3 .NET encryption client padding oracle allows object decryption",
      "what_changed": "AWS published CVE-2026-110310 on 14 October 2026, disclosing a padding oracle vulnerability in the Amazon S3 Encryption Client for .NET versions 2.1.0 and later, 3.0.0-3.2.1, and 4.0.0-4.0.2. An attacker with read access to encrypted S3 objects can alter metadata to force PKCS#1 v1.5 padding, then use a Bleichenbacher attack to recover the RSA-wrapped envelope key and decrypt the object.",
      "why_matters": "Any S3 bucket using client-side encryption with the affected .NET SDK versions is vulnerable to decryption by anyone who can read the encrypted objects. The attacker does not need write access to the bucket itself, only the ability to modify object metadata and perform repeated decryption attempts against the padding oracle.",
      "what_to_do": "Identify all services using the Amazon S3 Encryption Client for .NET in the affected version ranges. Check AWS's security bulletin 2026-135-AWS for patched versions and upgrade immediately. If you cannot patch this week, audit S3 bucket policies to ensure encrypted objects are not readable by untrusted principals.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-135-aws/",
      "published_at": "2026-10-15T04:42:17.437641+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/5d6e6508-2ab6-430a-b535-bfb220e028d4",
      "affects": [
        {
          "id": "cve-2026-110310",
          "type": "cve",
          "label": "CVE-2026-110310"
        },
        {
          "id": "aws",
          "type": "provider",
          "label": "aws"
        },
        {
          "id": "nugetawssdk-s3",
          "type": "package",
          "label": "nuget:AWSSDK.S3",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "d0cfb2d1-3e60-4c60-83a1-b5f75fb9c775",
      "channel": "security_advisory",
      "headline": "CISA adds Cisco email gateway path traversal to KEV catalog",
      "what_changed": "CVE-2026-76519, a relative path traversal vulnerability in Cisco Secure Email Gateway, was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-14 with a remediation deadline of 2026-10-17.",
      "why_matters": "Active exploitation is confirmed — that is what KEV listing means — and email gateways sit at the perimeter with access to all inbound mail. A path traversal in this position can expose message content, configuration, or credentials.",
      "what_to_do": "Check your asset inventory for Cisco Secure Email Gateway instances by 2026-10-17. If you run it, apply Cisco's published mitigation immediately or discontinue use per BOD 26-04. Federal agencies must comply; private sector should treat the deadline as the window before widespread tooling.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-14T21:44:53.506634+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/d0cfb2d1-3e60-4c60-83a1-b5f75fb9c775",
      "affects": [
        {
          "id": "cve-2026-76519",
          "type": "cve",
          "label": "CVE-2026-76519"
        },
        {
          "id": "cisco-secure-email-gateway",
          "type": "product",
          "label": "cisco secure email gateway",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-17",
      "time_to_correct": null
    },
    {
      "id": "d10e2ab2-5110-4458-85d8-1e078221bbf7",
      "channel": "security_advisory",
      "headline": "CISA adds Ahsay AhsayCBS command injection to KEV catalog",
      "what_changed": "CVE-2026-105134, a command injection vulnerability in Ahsay AhsayCBS backup and recovery software, was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-14. The due date for federal agencies is 2026-10-17.",
      "why_matters": "This vulnerability is being actively exploited in the wild. Command injection flaws allow attackers to execute arbitrary commands on the server, typically leading to full system compromise. CISA only adds vulnerabilities to the KEV catalog when exploitation is confirmed.",
      "what_to_do": "Check if you run Ahsay AhsayCBS. If yes, apply vendor mitigations by 2026-10-17 per CISA BOD 26-04 requirements, or discontinue use if mitigations are unavailable. Prioritize internet-facing instances.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-14T21:44:42.625116+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/d10e2ab2-5110-4458-85d8-1e078221bbf7",
      "affects": [
        {
          "id": "cve-2026-105134",
          "type": "cve",
          "label": "CVE-2026-105134"
        },
        {
          "id": "ahsaycbs",
          "type": "product",
          "label": "AhsayCBS",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-17",
      "time_to_correct": null
    },
    {
      "id": "ea89b466-9dcb-4a91-9221-25f73d97e6d5",
      "channel": "security_advisory",
      "headline": "CISA adds Ahsay AhsayCBS authentication bypass, due 17 October",
      "what_changed": "CVE-2026-105133, an improper authentication vulnerability in Ahsay AhsayCBS backup software, was added to CISA's Known Exploited Vulnerabilities catalog on 14 October 2026 with a remediation deadline of 17 October 2026. CISA's required action references BOD 26-04 compliance and forensics triage requirements.",
      "why_matters": "AhsayCBS is backup and recovery infrastructure. An authentication bypass in this layer means an attacker can access or manipulate backup data without credentials, which defeats disaster recovery controls and enables ransomware operators to destroy the last line of defense before encrypting production systems.",
      "what_to_do": "Confirm whether you run AhsayCBS in any environment by 17 October. If present, apply vendor mitigations per CISA BOD 26-04 or discontinue use if no mitigation exists. If the product is internet-exposed, prioritize forensic triage per CISA's requirements to determine whether exploitation has already occurred.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security"
      ],
      "confidence": 0.85,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-14T21:44:31.407241+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/ea89b466-9dcb-4a91-9221-25f73d97e6d5",
      "affects": [
        {
          "id": "cve-2026-105133",
          "type": "cve",
          "label": "CVE-2026-105133"
        },
        {
          "id": "ahsaycbs",
          "type": "product",
          "label": "AhsayCBS",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-17",
      "time_to_correct": null
    },
    {
      "id": "bcbfafa5-b378-4158-9569-baaeb6e6f6ec",
      "channel": "security_advisory",
      "headline": "CISA adds PAN-OS code injection CVE-2026-0322 to KEV catalog",
      "what_changed": "CISA added CVE-2026-0322 to the Known Exploited Vulnerabilities catalog on 2026-10-14. The vulnerability is a code injection flaw in Palo Alto Networks PAN-OS. The due date for federal agencies is 2026-10-17. CISA's required action references BOD 26-04 compliance and forensics triage requirements.",
      "why_matters": "Inclusion in the KEV catalog means this vulnerability is being actively exploited in the wild. Code injection in PAN-OS — a firewall and network security platform — gives attackers the ability to execute arbitrary code on infrastructure that sits at the network perimeter. The three-day window indicates CISA considers the threat immediate.",
      "what_to_do": "Check your PAN-OS inventory against the affected versions in Palo Alto's advisory for CVE-2026-0322. If exposed, apply vendor mitigations by 2026-10-17. If you provide cloud services using PAN-OS, follow BOD 26-04 patching timelines or discontinue use if mitigations are unavailable.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-14T21:44:19.54296+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/bcbfafa5-b378-4158-9569-baaeb6e6f6ec",
      "affects": [
        {
          "id": "cve-2026-0322",
          "type": "cve",
          "label": "CVE-2026-0322"
        },
        {
          "id": "pan-os",
          "type": "product",
          "label": "PAN-OS",
          "unmapped": true
        },
        {
          "id": "palo-alto-networks",
          "type": "provider",
          "label": "Palo Alto Networks",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-17",
      "time_to_correct": null
    },
    {
      "id": "2fc4875b-00de-47c3-b58e-883d213e40eb",
      "channel": "security_advisory",
      "headline": "Application Integration privilege escalation patched August 27",
      "what_changed": "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_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.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security"
      ],
      "confidence": 0.85,
      "source_name": "Google Cloud security bulletins",
      "source_url": "https://docs.cloud.google.com/support/bulletins/index#gcp-2026-068",
      "published_at": "2026-10-14T17:13:41.614127+00:00",
      "corrected_at": "2026-10-15T01:38:39.695108+00:00",
      "correction": "CORRECTION: Google's GCP-2026-068 bulletin states that CVE-2026-85298 in Application Integration was patched on August 27, 2026 and that no customer action is required. RADAR's ACTION NEEDED / VERIFY_EXPOSURE framing, the triage claim that platform leads must verify patch status, and the mandatory historical Cloud Audit Logs review in WHAT TO DO went beyond the source and should not be treated as Google requirements. Google requires no customer patch-status verification or historical log review for this bulletin. Optional RADAR defense-in-depth advice: teams with a specific concern about past service account misuse may choose to review relevant Cloud Audit Logs under their own security procedures. This optional advice is RADAR's, not Google's. The original article and source evidence are retained below as the historical record.",
      "correction_cause": "writer_overreach",
      "url": "https://radar.trulysovereign.com/items/2fc4875b-00de-47c3-b58e-883d213e40eb",
      "affects": [
        {
          "id": "application-integration",
          "type": "product",
          "label": "application integration",
          "unmapped": true
        },
        {
          "id": "cve-2026-85298",
          "type": "cve",
          "label": "CVE-2026-85298"
        },
        {
          "id": "google-cloud",
          "type": "provider",
          "label": "google cloud"
        }
      ],
      "action_due": null,
      "time_to_correct": "8h 25m"
    },
    {
      "id": "bb1277fe-480c-4c08-bf1d-86148c7cf3b3",
      "channel": "security_advisory",
      "headline": "CISA adds Windows command injection CVE to KEV catalog",
      "what_changed": "CVE-2026-96951, a command injection vulnerability in Microsoft Windows, was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-13. CISA set a due date of 2026-10-16 for federal agencies to apply mitigations per BOD 26-04.",
      "why_matters": "Command injection vulnerabilities allow remote code execution. CISA only adds vulnerabilities to the KEV catalog when they have evidence of active exploitation in the wild. The three-day window indicates urgency.",
      "what_to_do": "Check your Windows systems against CVE-2026-96951 today. If exposed, apply Microsoft's published mitigations by 2026-10-16. If you cannot mitigate, isolate or disconnect affected systems until you can patch.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-13T22:48:48.816158+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/bb1277fe-480c-4c08-bf1d-86148c7cf3b3",
      "affects": [
        {
          "id": "cve-2026-96951",
          "type": "cve",
          "label": "CVE-2026-96951"
        },
        {
          "id": "microsoft",
          "type": "provider",
          "label": "microsoft",
          "unmapped": true
        },
        {
          "id": "windows",
          "type": "product",
          "label": "windows",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-16",
      "time_to_correct": null
    },
    {
      "id": "069e8217-ab8b-4775-a826-f440e676c8bb",
      "channel": "security_advisory",
      "headline": "CISA adds Ivanti Connect Secure auth bypass to KEV, patch due October 16",
      "what_changed": "CVE-2026-104935, an authentication bypass vulnerability in Ivanti Connect Secure, was added to CISA's Known Exploited Vulnerabilities catalog on October 13, 2026. Federal agencies must apply mitigations by October 16, 2026 per Binding Operational Directive 26-04.",
      "why_matters": "This is a known-exploited authentication bypass in VPN gateway software. An attacker can gain unauthorized access without valid credentials. CISA only adds vulnerabilities to KEV when exploitation is confirmed in the wild, meaning active threat actors are already using this.",
      "what_to_do": "Check your Ivanti Connect Secure inventory against the affected versions in Ivanti's advisory. If exposed, apply the vendor's mitigations by October 16 or disconnect the system. Run CISA's forensics triage to confirm you were not already compromised.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "CISA Known Exploited Vulnerabilities",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "published_at": "2026-10-13T22:48:38.597325+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/069e8217-ab8b-4775-a826-f440e676c8bb",
      "affects": [
        {
          "id": "cve-2026-104935",
          "type": "cve",
          "label": "CVE-2026-104935"
        },
        {
          "id": "ivanti-connect-secure",
          "type": "product",
          "label": "ivanti connect secure",
          "unmapped": true
        }
      ],
      "action_due": "2026-10-16",
      "time_to_correct": null
    },
    {
      "id": "1df8a326-2157-425a-bad9-595ae9641187",
      "channel": "security_advisory",
      "headline": "GitLab 19.3.5 replaces broken 19.3.4 patch release",
      "what_changed": "GitLab released 19.3.5 on October 12, 2026, replacing 19.3.4 which had a bug affecting merge request pages when the Ona integration is enabled. All CVE impact statements now list 19.3.5 as the fixed version instead of 19.3.4. The release addresses 26 CVEs including CVE-2026-97229 (CVSS 10.0, unauthenticated RCE via CI/CD regex), CVE-2026-92883 (CVSS 8.7, XSS in syntax highlighting), CVE-2026-16301 (CVSS 8.5, unauthorized protected branch pipeline execution), and CVE-2026-14814 (CVSS 8.2, cache poisoning exposing CI/CD secrets).",
      "why_matters": "If you patched to 19.3.4, merge request pages are broken for any installation using the Ona integration. If you have not patched yet, you are running a version with a critical unauthenticated remote code execution vulnerability (CVSS 10.0) that allows arbitrary code execution via a crafted CI/CD regex, plus multiple high-severity issues exposing secrets and allowing unauthorized pipeline execution.",
      "what_to_do": "If you are on 19.3.4 with Ona integration enabled, upgrade to 19.3.5 immediately to restore merge request functionality. If you are on any 19.3.x version before 19.3.5, upgrade to 19.3.5 to patch the critical RCE and other vulnerabilities. Self-managed installations on 19.2.x or 19.4.x should upgrade to 19.2.8 or 19.4.2 respectively.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitLab patch releases",
      "source_url": "https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/",
      "published_at": "2026-10-13T02:46:44.851752+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/1df8a326-2157-425a-bad9-595ae9641187",
      "affects": [
        {
          "id": "gitlab",
          "type": "product",
          "label": "gitlab",
          "unmapped": true
        },
        {
          "id": "cve-2026-97229",
          "type": "cve",
          "label": "CVE-2026-97229"
        },
        {
          "id": "cve-2026-92883",
          "type": "cve",
          "label": "CVE-2026-92883"
        },
        {
          "id": "cve-2026-16301",
          "type": "cve",
          "label": "CVE-2026-16301"
        },
        {
          "id": "cve-2026-14814",
          "type": "cve",
          "label": "CVE-2026-14814"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "0344916f-4587-4a60-9427-aa21198d7d20",
      "channel": "security_advisory",
      "headline": "Envoy DoS in Cloud Service Mesh when path mutated after routing",
      "what_changed": "Google published GCP-2026-067 on 2026-10-12, disclosing a high-severity DoS vulnerability in Envoy Proxy (envoyproxy/envoy#47841). The flaw triggers when an HTTP filter mutates the :path header after route selection on routes configured with prefix_rewrite.",
      "why_matters": "Cloud Service Mesh control plane components running affected Envoy versions can be crashed by crafted requests that exploit this path mutation sequence. You cannot patch Envoy directly in a managed service — Google must deploy the fix.",
      "what_to_do": "Check the linked Cloud Service Mesh security bulletin for affected versions and Google's remediation timeline. If you use ext_proc filters with route_cache_action: RETAIN on prefix_rewrite routes, verify whether your mesh version is vulnerable and whether Google has patched your control plane.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security"
      ],
      "confidence": 0.85,
      "source_name": "Google Cloud security bulletins",
      "source_url": "https://docs.cloud.google.com/support/bulletins/index#gcp-2026-067",
      "published_at": "2026-10-13T02:46:27.375636+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/0344916f-4587-4a60-9427-aa21198d7d20",
      "affects": [
        {
          "id": "envoyproxy/envoy47841",
          "type": "cve",
          "label": "envoyproxy/envoy#47841",
          "unmapped": true
        },
        {
          "id": "cloud-service-mesh",
          "type": "product",
          "label": "cloud service mesh",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "8e3f35fe-5499-4f71-be4c-ccbc16c2628c",
      "channel": "security_advisory",
      "headline": "GitLab critical RCE via CI/CD regex, 23 other CVEs patched",
      "what_changed": "GitLab released emergency patches 19.4.2, 19.3.4, and 19.2.8 on October 12, 2026. CVE-2026-97229 is an unauthenticated remote code execution vulnerability (CVSS 10.0) in the CI/CD regular expression compiler affecting all GitLab CE/EE versions from 19.2.0 onward. The release also patches 23 additional CVEs including high-severity authorization bypasses in CI/CD pipelines (CVE-2026-16301, CVSS 8.5), cache poisoning enabling environment variable exposure (CVE-2026-14814, CVSS 8.2), and LLM prompt injection in GitLab Duo Agent Platform (CVE-2026-96893, CVSS 7.3). Self-managed installations require immediate upgrade; GitLab.com is already patched.",
      "why_matters": "An unauthenticated attacker can execute arbitrary code on any unpatched GitLab server by submitting a crafted regular expression in a CI/CD configuration file. Multiple high-severity flaws allow authenticated users with developer access to run unauthorized pipelines on protected branches, poison caches to steal CI secrets, and inject commands into AI agent contexts. GitLab is source control and CI/CD infrastructure — compromise means access to all code, credentials, and build artifacts.",
      "what_to_do": "Upgrade self-managed GitLab installations to 19.4.2, 19.3.4, or 19.2.8 immediately. Single-node deployments will experience downtime during the upgrade due to required database migrations. Multi-node deployments can follow zero-downtime procedures. Note that 19.3.4 has a known bug affecting merge request pages when the Ona integration is enabled; 19.3.5 will follow. GitLab Dedicated customers do not need to act.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api",
        "deprecation"
      ],
      "confidence": 0.95,
      "source_name": "GitLab patch releases",
      "source_url": "https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/",
      "published_at": "2026-10-12T15:28:31.138922+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/8e3f35fe-5499-4f71-be4c-ccbc16c2628c",
      "affects": [
        {
          "id": "gitlab-ce",
          "type": "product",
          "label": "gitlab ce",
          "unmapped": true
        },
        {
          "id": "gitlab-ee",
          "type": "product",
          "label": "gitlab ee",
          "unmapped": true
        },
        {
          "id": "cve-2026-97229",
          "type": "cve",
          "label": "CVE-2026-97229"
        },
        {
          "id": "cve-2026-92883",
          "type": "cve",
          "label": "CVE-2026-92883"
        },
        {
          "id": "cve-2026-16301",
          "type": "cve",
          "label": "CVE-2026-16301"
        },
        {
          "id": "cve-2026-14814",
          "type": "cve",
          "label": "CVE-2026-14814"
        },
        {
          "id": "cve-2026-81839",
          "type": "cve",
          "label": "CVE-2026-81839"
        },
        {
          "id": "cve-2026-96893",
          "type": "cve",
          "label": "CVE-2026-96893"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "df9f4b54-8ff2-4c21-8de0-134e1d789e54",
      "channel": "security_advisory",
      "headline": "pyLoad authentication bypass in API key validation",
      "what_changed": "GitHub published GHSA-r44w-v6gf-x3p6 on 2026-10-09, a high-severity authentication bypass in pyload-ng's API key validation (check_apikey cache). The vulnerability is patched in version 0.5.0b3.dev101.",
      "why_matters": "An attacker can bypass API authentication entirely, gaining unauthorized access to pyLoad's API without valid credentials. This exposes download management operations, configuration, and potentially stored credentials in any deployment where the API is reachable.",
      "what_to_do": "Grep your dependency manifests and container images for pyload-ng. If found, update to 0.5.0b3.dev101 or later. If pyLoad is deployed with an exposed API endpoint, treat this as an active exposure until patched.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:35:23.249395+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/df9f4b54-8ff2-4c21-8de0-134e1d789e54",
      "affects": [
        {
          "id": "pypipyload-ng",
          "type": "package",
          "label": "pypi:pyload-ng",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "56b7aabb-ea86-4e60-a8a4-f9d1647e0008",
      "channel": "security_advisory",
      "headline": "Strawberry GraphQL authorization bypass in synchronous permission checks",
      "what_changed": "CVE-2026-107728 published 9 October 2026 for strawberry-graphql. Synchronous permission checks incorrectly treat awaitable authorization results as truthy, allowing unauthorized access. Fixed in version 0.326.1.",
      "why_matters": "Authorization logic fails open. Any GraphQL resolver using synchronous permission checks with async authorization functions grants access regardless of the actual authorization result. An attacker can access protected fields and mutations without valid permissions.",
      "what_to_do": "Upgrade strawberry-graphql to 0.326.1 or later. If you use synchronous permission checks with async authorization functions, audit access logs for unauthorized queries between your deployment date and the upgrade.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:35:14.759104+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/56b7aabb-ea86-4e60-a8a4-f9d1647e0008",
      "affects": [
        {
          "id": "pypistrawberry-graphql",
          "type": "package",
          "label": "pypi:strawberry-graphql",
          "unmapped": true
        },
        {
          "id": "cve-2026-107728",
          "type": "cve",
          "label": "CVE-2026-107728"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "4968acfb-0e94-42b4-86ae-46c726ca45fb",
      "channel": "security_advisory",
      "headline": "pyLoad session persists after privilege revocation or password change",
      "what_changed": "GHSA-jq7h-wrvp-3rgx published 9 October 2026 reports that pyload-ng does not invalidate active sessions when a user's privileges are revoked or password is changed through the REST API. Severity is high. No patched version is listed.",
      "why_matters": "An administrator who revokes a user's access or forces a password reset cannot actually terminate that user's active session. The user retains full access until the session expires naturally or the server restarts, making privilege revocation and credential rotation ineffective as security controls.",
      "what_to_do": "Check whether you are running pyload-ng in production. If so, restart the service to force session invalidation after any privilege change or password reset until a patch is available, and monitor GHSA-jq7h-wrvp-3rgx for a fixed version.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:35:06.268916+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/4968acfb-0e94-42b4-86ae-46c726ca45fb",
      "affects": [
        {
          "id": "pypipyload-ng",
          "type": "package",
          "label": "pypi:pyload-ng",
          "unmapped": true
        },
        {
          "id": "ghsa-jq7h-wrvp-3rgx",
          "type": "cve",
          "label": "GHSA-jq7h-wrvp-3rgx",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "ae3b7edd-d3ad-43da-af76-17328d81e6cb",
      "channel": "security_advisory",
      "headline": "pyload-ng tar extraction creates device nodes without filter",
      "what_changed": "GitHub published GHSA-fr26-jjhm-638c on 2026-10-09, a high-severity advisory for pyload-ng. The package calls tarfile.extractall() without a filter parameter, allowing tar archives to create device nodes and FIFOs during extraction. No patched version is listed.",
      "why_matters": "An attacker-controlled tar archive can write device nodes or named pipes to the filesystem during extraction, which can be used to read sensitive files, block processes, or escalate privileges depending on where pyload-ng extracts archives and what permissions it runs under.",
      "what_to_do": "Grep your dependency trees for pyload-ng and confirm whether you run it. If you do, check whether it processes tar archives from untrusted sources. No patch is available yet; if you are exposed, consider disabling tar upload/processing or running pyload-ng in a container with device node creation blocked until a fix ships.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:34:55.623993+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/ae3b7edd-d3ad-43da-af76-17328d81e6cb",
      "affects": [
        {
          "id": "pypipyload-ng",
          "type": "package",
          "label": "pypi:pyload-ng",
          "unmapped": true
        },
        {
          "id": "ghsa-fr26-jjhm-638c",
          "type": "cve",
          "label": "GHSA-fr26-jjhm-638c",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "57f0c5e2-dabd-4e1e-9efa-18e89449d510",
      "channel": "security_advisory",
      "headline": "pyLoad API permission change does not invalidate active sessions",
      "what_changed": "GHSA-889w-m37p-88m5 published 9 October 2026 for pyload-ng. High severity. Api.set_user_permission function fails to invalidate the target user's session when permissions change. No patched version listed in the advisory.",
      "why_matters": "A user whose permissions are revoked retains their active session and can continue operating with the old permission set until the session expires naturally. If you demote or restrict a user account, the change does not take effect until they log out or the session times out.",
      "what_to_do": "Check whether pyload-ng is in your dependency tree. If present, manually invalidate sessions after any permission change — force logout or restart the service — until a patched version is released. Monitor GHSA-889w-m37p-88m5 for the fix.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.75,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:34:44.219647+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/57f0c5e2-dabd-4e1e-9efa-18e89449d510",
      "affects": [
        {
          "id": "pypipyload-ng",
          "type": "package",
          "label": "pypi:pyload-ng",
          "unmapped": true
        },
        {
          "id": "ghsa-889w-m37p-88m5",
          "type": "cve",
          "label": "GHSA-889w-m37p-88m5",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "5ae4d7e1-52ab-4e80-b3e2-5d911e40ff43",
      "channel": "security_advisory",
      "headline": "pyload-ng getUserData endpoint allows admin password brute-force",
      "what_changed": "GitHub published GHSA-68w4-83fh-f2w8 on 2026-10-09, rating it high severity. The getUserData/get_userdata endpoint in pyload-ng is exposed at Perms.ANY permission level, allowing any authenticated account to brute-force the administrator password. No patched version is available.",
      "why_matters": "Any user with valid credentials to your pyload-ng instance can attempt unlimited password guesses against the admin account. Successful brute-force grants full administrative control over the download manager and any systems it can access.",
      "what_to_do": "Check whether you run pyload-ng in production or internal infrastructure. If you do, restrict network access to the instance to trusted IPs only, disable or remove non-admin user accounts, and monitor authentication logs for repeated failed admin login attempts until a patch is released.",
      "severity": "action_needed",
      "action_type": "mitigate",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-10T12:34:33.79713+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/5ae4d7e1-52ab-4e80-b3e2-5d911e40ff43",
      "affects": [
        {
          "id": "pypipyload-ng",
          "type": "package",
          "label": "pypi:pyload-ng",
          "unmapped": true
        },
        {
          "id": "ghsa-68w4-83fh-f2w8",
          "type": "cve",
          "label": "GHSA-68w4-83fh-f2w8",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "5af1c9ad-9ed0-4589-9408-c8b128735ae5",
      "channel": "security_advisory",
      "headline": "@tinacms/web-components stored XSS via unvalidated link URLs",
      "what_changed": "GitHub published CVE-2026-108260 on 9 October 2026, a high-severity stored XSS vulnerability in @tinacms/web-components. The tina-markdown component writes rich-text link URLs directly into href attributes without scheme validation. Version 0.2.1 patches the issue.",
      "why_matters": "An attacker who can edit content rendered by tina-markdown can inject javascript: URLs that execute in the context of your application when a user clicks the link. This is stored XSS — the payload persists in your content and fires for every visitor.",
      "what_to_do": "Check package.json and lock files for @tinacms/web-components. If you are running any version before 0.2.1, update to 0.2.1 or later. If you use tina-markdown to render user-supplied or CMS-managed content, audit existing content for javascript: and data: scheme URLs and remove them.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — npm",
      "source_url": "https://api.github.com/advisories?ecosystem=npm&severity=high&per_page=100",
      "published_at": "2026-10-10T12:34:18.96864+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/5af1c9ad-9ed0-4589-9408-c8b128735ae5",
      "affects": [
        {
          "id": "npm@tinacms/web-components",
          "type": "package",
          "label": "npm:@tinacms/web-components",
          "unmapped": true
        },
        {
          "id": "cve-2026-108260",
          "type": "cve",
          "label": "CVE-2026-108260"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "429fe025-8405-41a3-b55a-c73ecc10adca",
      "channel": "security_advisory",
      "headline": "AWS Tools for PowerShell logs cleartext console passwords before 5.0.306",
      "what_changed": "CVE-2026-107783 disclosed on 9 October 2026. AWS Tools for PowerShell versions up to and including 5.0.305 write IAM user cleartext AWS Management Console passwords to command output and log artifacts. Fixed in version 5.0.306.",
      "why_matters": "Local users with access to PowerShell logs or command history can recover IAM credentials in plaintext. These credentials grant console access to AWS accounts with whatever permissions that IAM user holds.",
      "what_to_do": "Upgrade AWS Tools for PowerShell to version 5.0.306 or later. Rotate console passwords for any IAM users whose credentials were used with affected versions, and audit log files on systems running those versions for exposed credentials.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-132-aws/",
      "published_at": "2026-10-10T05:55:48.04291+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/429fe025-8405-41a3-b55a-c73ecc10adca",
      "affects": [
        {
          "id": "cve-2026-107783",
          "type": "cve",
          "label": "CVE-2026-107783"
        },
        {
          "id": "aws-tools-for-powershell",
          "type": "package",
          "label": "AWS Tools for PowerShell",
          "unmapped": true
        },
        {
          "id": "aws",
          "type": "provider",
          "label": "aws"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "19c82105-5835-4a14-a76e-024de3b938a5",
      "channel": "security_advisory",
      "headline": "Authorization bypass in AWS Amplify GraphQL resolvers allows cross-tenant data reads",
      "what_changed": "AWS disclosed CVE-2026-108096 on 9 October 2026, an authorization flaw in @aws-amplify/graphql-index-transformer that allows authenticated users to read other users' records via crafted GraphQL queries. Affected versions: graphql-index-transformer 2.2.0 to 3.1.1, graphql-api-construct 1.4.0 to 1.21.3, data-construct below 1.17.4. Fixed versions: 3.1.2, 1.21.4, and 1.17.4 respectively.",
      "why_matters": "If you use AWS Amplify API Category to generate GraphQL APIs with per-user authorization rules, authenticated attackers can bypass those rules and read data belonging to other tenants or users. This breaks the security model of any multi-tenant application relying on Amplify's generated resolvers for data isolation.",
      "what_to_do": "Check package.json or yarn.lock for the three named packages. If any are present in the affected version ranges, upgrade to the fixed versions (graphql-index-transformer 3.1.2+, graphql-api-construct 1.21.4+, data-construct 1.17.4+) and redeploy your AppSync API stack.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-133-aws/",
      "published_at": "2026-10-10T05:55:16.119529+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/19c82105-5835-4a14-a76e-024de3b938a5",
      "affects": [
        {
          "id": "cve-2026-108096",
          "type": "cve",
          "label": "CVE-2026-108096"
        },
        {
          "id": "npm@aws-amplify/graphql-index-transformer",
          "type": "package",
          "label": "npm:@aws-amplify/graphql-index-transformer",
          "unmapped": true
        },
        {
          "id": "npm@aws-amplify/graphql-api-construct",
          "type": "package",
          "label": "npm:@aws-amplify/graphql-api-construct",
          "unmapped": true
        },
        {
          "id": "npm@aws-amplify/data-construct",
          "type": "package",
          "label": "npm:@aws-amplify/data-construct",
          "unmapped": true
        },
        {
          "id": "aws",
          "type": "provider",
          "label": "aws"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "c4a08adf-85f5-4f80-9c1a-f48ed975c85e",
      "channel": "security_advisory",
      "headline": "PraisonAI agents package SSRF bypass exposes internal responses",
      "what_changed": "GitHub published CVE-2026-61430 on 8 October 2026, a high-severity SSRF vulnerability in praisonaiagents. The web_crawl function's protection can be bypassed via DNS rebinding, allowing disclosure of internal network responses. First patched version is 1.6.78.",
      "why_matters": "If you run praisonaiagents below 1.6.78, an attacker can use DNS rebinding to make the agent crawl internal endpoints and return their responses, exposing internal APIs, metadata services, or admin interfaces that should not be reachable from outside.",
      "what_to_do": "Grep your dependencies for praisonaiagents and check the version. If below 1.6.78, update to 1.6.78 or later this week. If you cannot update immediately, disable or firewall the web_crawl feature until you can.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:52.411251+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/c4a08adf-85f5-4f80-9c1a-f48ed975c85e",
      "affects": [
        {
          "id": "pypipraisonaiagents",
          "type": "package",
          "label": "pypi:praisonaiagents",
          "unmapped": true
        },
        {
          "id": "cve-2026-61430",
          "type": "cve",
          "label": "CVE-2026-61430"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "b6665400-b896-46fa-b661-d527fdd81535",
      "channel": "security_advisory",
      "headline": "PraisonAI agents package executes unverified Python files on plugin load",
      "what_changed": "GitHub published CVE-2026-61446 on 8 October 2026, rating it high severity. The praisonaiagents package auto-discovers and executes arbitrary Python files during plugin loading without verification. Version 1.6.78 patches the vulnerability.",
      "why_matters": "Any deployment running praisonaiagents before 1.6.78 will execute Python code from the plugin discovery path without validation. An attacker who can write to that path — through a compromised dependency, a shared filesystem, or a supply chain insertion — achieves arbitrary code execution in the agent runtime.",
      "what_to_do": "Grep your dependency trees for praisonaiagents and check the installed version. If you are running anything before 1.6.78, update to 1.6.78 or later in this patch cycle. If you cannot update immediately, disable plugin auto-discovery or restrict write access to the plugin path until you can.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:41.726245+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/b6665400-b896-46fa-b661-d527fdd81535",
      "affects": [
        {
          "id": "pypipraisonaiagents",
          "type": "package",
          "label": "pypi:praisonaiagents",
          "unmapped": true
        },
        {
          "id": "cve-2026-61446",
          "type": "cve",
          "label": "CVE-2026-61446"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "c4f9161e-69da-4a35-a43f-761498b3d45c",
      "channel": "security_advisory",
      "headline": "PraisonAI 4.6.78 patches unauthenticated MCP transport exposing tool calls",
      "what_changed": "GitHub published CVE-2026-61427 on 8 October 2026. PraisonAI's MCP HTTP-stream transport runs unauthenticated by default, exposing tool enumeration and an unvalidated tool-call surface. Severity is high. Version 4.6.78 patches the vulnerability.",
      "why_matters": "An unauthenticated transport means any network actor can enumerate available tools and invoke them without credentials. If PraisonAI agents have access to internal APIs, databases, or file systems through MCP tools, those surfaces are now remotely callable without authentication.",
      "what_to_do": "Upgrade praisonai to 4.6.78 or later. If you cannot upgrade immediately, disable the MCP HTTP-stream transport or place it behind authenticated reverse proxy until you can patch.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:31.876021+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/c4f9161e-69da-4a35-a43f-761498b3d45c",
      "affects": [
        {
          "id": "pypipraisonai",
          "type": "package",
          "label": "pypi:praisonai",
          "unmapped": true
        },
        {
          "id": "cve-2026-61427",
          "type": "cve",
          "label": "CVE-2026-61427"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "1fd0c589-28ad-4778-8878-58a4d6c59f50",
      "channel": "security_advisory",
      "headline": "Pydantic AI web chat UI allows remote sites to trigger agent tool execution",
      "what_changed": "CVE-2026-107295 published 8 October 2026. The web chat UI exposed by Agent.to_web() and clai web in pydantic-ai and pydantic-ai-slim allows a website visited by the developer to trigger agent runs and execute server-side tools on the local chat endpoint. Patched in versions 1.107.4 and 2.28.0.",
      "why_matters": "If you run the local web UI during development, a malicious site in another browser tab can execute arbitrary agent tools on your machine without interaction. This is server-side execution, not just data exfiltration — any tool the agent has access to can be invoked remotely.",
      "what_to_do": "Update pydantic-ai or pydantic-ai-slim to 1.107.4 (1.x branch) or 2.28.0 (2.x branch). If you do not use Agent.to_web() or clai web, verify your dependency tree does not pull in the vulnerable versions through another package.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:22.49829+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/1fd0c589-28ad-4778-8878-58a4d6c59f50",
      "affects": [
        {
          "id": "pypipydantic-ai",
          "type": "package",
          "label": "pypi:pydantic-ai",
          "unmapped": true
        },
        {
          "id": "pypipydantic-ai-slim",
          "type": "package",
          "label": "pypi:pydantic-ai-slim",
          "unmapped": true
        },
        {
          "id": "cve-2026-107295",
          "type": "cve",
          "label": "CVE-2026-107295"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "6be72fdd-221e-49d2-bee4-17002f315eff",
      "channel": "security_advisory",
      "headline": "PraisonAI shell command allowlist bypass fixed in 4.6.78",
      "what_changed": "CVE-2026-61434 published 8 October 2026 for praisonai package. High severity shell command execution vulnerability via find -exec built-in action bypasses the command allowlist. Fixed in version 4.6.78.",
      "why_matters": "An attacker can execute arbitrary shell commands despite allowlist controls by abusing find's -exec flag. This defeats the security boundary the allowlist is meant to enforce, allowing full command execution in contexts where only specific commands should be permitted.",
      "what_to_do": "Upgrade praisonai to 4.6.78 or later. If you use praisonai's command execution features, audit logs for find commands with -exec flags to check for exploitation attempts before the patch.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:12.311563+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/6be72fdd-221e-49d2-bee4-17002f315eff",
      "affects": [
        {
          "id": "pypipraisonai",
          "type": "package",
          "label": "pypi:praisonai",
          "unmapped": true
        },
        {
          "id": "cve-2026-61434",
          "type": "cve",
          "label": "CVE-2026-61434"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "75bf2a91-8a3e-4b2c-b5e9-bab4c35b8de6",
      "channel": "security_advisory",
      "headline": "PraisonAI platform authorization bypass patched in 0.1.9",
      "what_changed": "GitHub published CVE-2026-61442 on 8 October 2026, a high-severity authorization bypass in praisonai-platform. Platform members can overwrite owner resources via PATCH routes and bypass project lead reassignment deletion. The vulnerability is patched in version 0.1.9.",
      "why_matters": "Any deployment running praisonai-platform below 0.1.9 allows non-owner users to escalate privileges and modify resources they should not control. This breaks access control assumptions in multi-user environments.",
      "what_to_do": "Upgrade praisonai-platform to 0.1.9 or later. If you run this package in production, audit recent PATCH activity for unauthorized resource modifications before upgrading.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:21:02.454078+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/75bf2a91-8a3e-4b2c-b5e9-bab4c35b8de6",
      "affects": [
        {
          "id": "pypipraisonai-platform",
          "type": "package",
          "label": "pypi:praisonai-platform",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "ce9dada2-e2aa-4a01-a263-42aa008360d8",
      "channel": "security_advisory",
      "headline": "PraisonAI agents package executes scripts without path validation",
      "what_changed": "GitHub published CVE-2026-61443 on 8 October 2026, a high-severity vulnerability in praisonaiagents. The SkillTools component executes scripts without validating file paths, allowing arbitrary script execution. Version 1.6.78 patches the issue.",
      "why_matters": "An attacker who can influence script paths passed to SkillTools can execute arbitrary code on the system running the agent. This bypasses intended containment and gives full process privileges to untrusted input.",
      "what_to_do": "Check your dependency tree for praisonaiagents. If present and below 1.6.78, update to 1.6.78 or later this week. If you cannot update immediately, audit all code paths that pass file arguments to SkillTools and ensure they reject user-controlled input.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:20:53.528176+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/ce9dada2-e2aa-4a01-a263-42aa008360d8",
      "affects": [
        {
          "id": "pypipraisonaiagents",
          "type": "package",
          "label": "pypi:praisonaiagents",
          "unmapped": true
        },
        {
          "id": "cve-2026-61443",
          "type": "cve",
          "label": "CVE-2026-61443"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "f8dd14a0-6874-4ade-b2dd-e2d1ec8b6ce0",
      "channel": "security_advisory",
      "headline": "PraisonAI 4.6.78 patches YAML injection in code generator",
      "what_changed": "CVE-2026-61433 published 8 October 2026. PraisonAI versions before 4.6.78 embed unescaped YAML fields directly into generated Python source code in the API deploy code generator. Severity rated high. First patched version is 4.6.78.",
      "why_matters": "An attacker controlling YAML input can inject arbitrary Python code that executes when the generated deployment code runs. This is a code generation vulnerability in an AI framework SDK — the generated code itself is the attack surface.",
      "what_to_do": "Upgrade praisonai to 4.6.78 or later if you use the API deploy code generator. If you cannot upgrade immediately, audit any generated deployment code for unescaped YAML content and do not run code generated from untrusted YAML sources.",
      "severity": "action_needed",
      "action_type": "patch_now",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.88,
      "source_name": "GitHub advisories — pip",
      "source_url": "https://api.github.com/advisories?ecosystem=pip&severity=high&per_page=100",
      "published_at": "2026-10-09T13:20:42.205134+00:00",
      "corrected_at": null,
      "correction": null,
      "correction_cause": null,
      "url": "https://radar.trulysovereign.com/items/f8dd14a0-6874-4ade-b2dd-e2d1ec8b6ce0",
      "affects": [
        {
          "id": "pypipraisonai",
          "type": "package",
          "label": "pypi:praisonai",
          "unmapped": true
        },
        {
          "id": "cve-2026-61433",
          "type": "cve",
          "label": "CVE-2026-61433"
        }
      ],
      "action_due": null,
      "time_to_correct": null
    },
    {
      "id": "6f99c484-f40d-4dbe-aff2-44a56b13179a",
      "channel": "security_advisory",
      "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_matters": "If 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_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.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.85,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-014-aws/",
      "published_at": "2026-09-24T19:12:53.652371+00:00",
      "corrected_at": "2026-09-24T22:33:48.308+00:00",
      "correction": "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.",
      "correction_cause": "source_changed_format",
      "url": "https://radar.trulysovereign.com/items/6f99c484-f40d-4dbe-aff2-44a56b13179a",
      "affects": [
        {
          "id": "cve-2026-5707",
          "type": "cve",
          "label": "CVE-2026-5707"
        },
        {
          "id": "cve-2026-5708",
          "type": "cve",
          "label": "CVE-2026-5708"
        },
        {
          "id": "cve-2026-5709",
          "type": "cve",
          "label": "CVE-2026-5709"
        },
        {
          "id": "research-and-engineering-studio",
          "type": "product",
          "label": "Research and Engineering Studio",
          "unmapped": true
        }
      ],
      "action_due": null,
      "time_to_correct": "3h 21m"
    },
    {
      "id": "ccfacdbd-790c-445d-99e5-1f00377f5dcc",
      "channel": "security_advisory",
      "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_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.",
      "severity": "action_needed",
      "action_type": "verify_exposure",
      "tags": [
        "security",
        "api"
      ],
      "confidence": 0.95,
      "source_name": "AWS security bulletins",
      "source_url": "https://aws.amazon.com/security/security-bulletins/rss/2026-020-aws/",
      "published_at": "2026-09-24T19:12:34.965137+00:00",
      "corrected_at": "2026-09-24T22:33:48.963+00:00",
      "correction": "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.",
      "correction_cause": "source_changed_format",
      "url": "https://radar.trulysovereign.com/items/ccfacdbd-790c-445d-99e5-1f00377f5dcc",
      "affects": [
        {
          "id": "cve-2026-7191",
          "type": "cve",
          "label": "CVE-2026-7191"
        },
        {
          "id": "qnabot-on-aws",
          "type": "product",
          "label": "QnABot on AWS",
          "unmapped": true
        },
        {
          "id": "npmstatic-eval",
          "type": "package",
          "label": "npm:static-eval",
          "unmapped": true
        },
        {
          "id": "aws",
          "type": "provider",
          "label": "aws"
        }
      ],
      "action_due": null,
      "time_to_correct": "3h 21m"
    }
  ]
}