{ "schema_version": 1, "kev_checked_at": "2026-10-24T00:14:05.818Z", "updated_at": "2026-10-23T21:15:06Z", "items": [ { "slug": "litellm-1-107-0", "url": "https://www.oktsec.com/radar/litellm-1-107-0", "title": "LiteLLM 1.107.0: check where it ran", "summary": "LiteLLM confirmed malicious PyPI and container artifacts. Removing the package does not revoke credentials it could access.", "body": "Search deployment records, image digests and CI caches. Determine whether the affected artifact actually executed and which secrets were reachable. Installation history alone does not establish what was accessed.\n\nThe vendor identifies malicious artifacts in public distribution channels. Its incident report distinguishes those artifacts from the official GitHub source and private enterprise registry. Consult the vendor timeline for the affected download windows.\n\nTreat execution on a host as a compromise investigation. Revoke credentials at the issuer and review associated sessions and usage. Rebuilding the application does not invalidate an exposed key.\n\nThe vendor warns that starting Python or pip in an affected environment can execute the payload again through startup files. Use a clean environment for investigation and recovery.", "audience": "Teams that installed version 1.107.0 or pulled affected container tags on October 21.", "agent_angle": "Model provider keys and agent credentials stored in the same environment belong in the investigation.", "kind": "supply_chain", "priority": "act_now", "triage": { "basis": "credentials_exposed", "reach": "package_execution", "reason": "A malicious package was distributed. If it executed, treat credentials accessible to that process as potentially exposed." }, "reported_on": "2026-10-21", "topics": [ "ai_agents", "cloud_secrets" ], "vendor": "LiteLLM", "products": [ "LiteLLM" ], "cves": [], "kev": [], "exploitation": "exploited", "patch": "partial", "action": "Identify affected executions, replace accessible credentials and rebuild from a clean environment.", "checklist": [ { "id": "scope", "title": "Find where it ran", "text": "Search images, lockfiles and CI caches for LiteLLM 1.107.0 and affected image tags. Establish whether the affected artifact executed." }, { "id": "action", "title": "Replace reachable credentials", "text": "If the artifact executed, identify and revoke the credentials it could access. Include model provider keys and relevant sessions." }, { "id": "evidence", "title": "Rebuild from a clean environment", "text": "Investigate and rebuild from a clean environment. Do not start Python or pip in an affected environment: the vendor warns that startup files can execute the payload again. Verify the replacement artifact or image digest before restoring service." } ], "affected": [ { "product": "PyPI package", "range": "litellm 1.107.0", "fixed_in": [ "Vendor recommends 1.106.2" ] }, { "product": "Container images", "range": "1.107.0 and moving tags during the incident window", "fixed_in": [ "Use a verified clean image digest" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T20:34:00Z", "updated_at": "2026-10-23T21:15:06Z", "last_verified_at": "2026-10-23T21:15:06Z", "sources": [ { "title": "October 21 supply chain incident", "url": "https://docs.litellm.ai/blog/security-incident-oct-21-2026", "publisher": "LiteLLM", "kind": "vendor", "checked_at": "2026-10-23T21:15:06Z" } ], "changelog": [ { "at": "2026-10-23T20:34:00Z", "text": "Initial local draft. Malicious distribution confirmed by the vendor; customer impact requires investigation." }, { "at": "2026-10-23T21:03:38Z", "text": "Added the response priority rationale and original disclosure date." }, { "at": "2026-10-23T21:15:06Z", "text": "Clarified the vendor warning against running Python or pip in an affected environment, and included this incident in AI and cloud credential coverage." } ] }, { "slug": "carliy0s-latin-american-financial-sector", "url": "https://www.oktsec.com/radar/carliy0s-latin-american-financial-sector", "title": "CARLIY0S: targeting Latin American banks", "summary": "Straiker reports AI supported attack operations targeting banks and payment providers in Latin America. Its reported target inventory is not a count of confirmed compromises.", "body": "Straiker describes an operation using multiple commercial models and reports a target set exceeding 400 financial institutions. Treat that figure as research about targeting, not confirmed victim totals.\n\nOktsec recommends using the report to focus existing exposure and access reviews.", "audience": "Banks, fintech companies and payment providers operating in Latin America.", "agent_angle": "The report describes commercial models used across attack tasks. It does not establish that every operation was autonomous.", "kind": "threat_activity", "priority": "monitor", "triage": { "basis": "regional_research", "reach": "unknown", "reason": "Regional threat research warrants exposure review. There is no single affected software version or universal patch to apply." }, "reported_on": "2026-10-21", "topics": [ "latam", "ai_offense", "ai_agents" ], "vendor": "Latin American financial services", "products": [ "Banking applications", "Payment services" ], "cves": [], "kev": [], "exploitation": "unknown", "patch": "not_applicable", "action": "Review exposed services, privileged access and model provider credentials.", "checklist": [ { "id": "scope", "title": "Identify relevant services", "text": "Map public financial services and third party integrations against your existing threat model." }, { "id": "action", "title": "Review access and credentials", "text": "Check unnecessary privileges, exposed secrets and unusual model provider use in systems relevant to the report." }, { "id": "evidence", "title": "Correlate with your evidence", "text": "Compare internal telemetry with the research. A named sector or target inventory does not establish compromise of your organization." } ], "affected": [], "verification": "single_source", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:08:44Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "CARLIY0S investigation", "url": "https://www.straiker.ai/blog/inside-carliy0s-how-cybercartel-used-multiple-ai-models-to-attack-latin-american-banks", "publisher": "Straiker", "kind": "research", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." }, { "at": "2026-10-23T21:08:44Z", "text": "Shortened the title and clarified the campaign scope for the incident workspace." } ] }, { "slug": "arista-velocloud-cve-2026-114625", "url": "https://www.oktsec.com/radar/arista-velocloud-cve-2026-114625", "title": "VeloCloud Orchestrator: active exploitation confirmed", "summary": "Arista reports exploitation of an authenticated SQL injection flaw. Operators of affected on premises deployments need to apply the vendor fix.", "body": "An authenticated tenant user can exploit the issue to impersonate a superuser operator. Arista says Hosted and Dedicated services have been patched. Organizations running VCO themselves must check their deployed release.\n\nOktsec recommends preserving authentication and administrative records before making changes, then checking for unexpected privileged activity. The advisory does not mean every Arista product is affected.", "audience": "Organizations operating their own VeloCloud Orchestrator.", "agent_angle": "No direct agent exposure is documented. Review network access paths used by agents where VCO manages their connectivity.", "kind": "vulnerability", "priority": "act_now", "triage": { "basis": "confirmed_exploitation", "reach": "authenticated", "reason": "Arista reports exploitation. A tenant account can reach operator privileges on an affected Orchestrator." }, "reported_on": "2026-10-21", "cvss": { "score": 9.9, "version": "3.1" }, "topics": [], "vendor": "Arista", "products": [ "VeloCloud Orchestrator" ], "cves": [ "CVE-2026-114625" ], "kev": [ { "cve": "CVE-2026-114625", "vendor": "Arista", "product": "VeloCloud Orchestrator", "title": "Arista VeloCloud Orchestrator SQL Injection Vulnerability", "description": "Arista VeloCloud Orchestrator on-prem contains a SQL injection vulnerability that may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator.", "date_added": "2026-10-23", "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.", "federal_due_date": "2026-10-26", "ransomware": "Unknown", "forensic_triage": "Yes" } ], "exploitation": "exploited", "patch": "available", "action": "Upgrade affected VCO deployments and review privileged account activity.", "checklist": [ { "id": "scope", "title": "Identify affected Orchestrators", "text": "Match the version of each on premises VeloCloud Orchestrator to Arista’s advisory. Distinguish these deployments from vendor managed services." }, { "id": "action", "title": "Verify the upgrade", "text": "Apply the fixed release for the deployed branch, then confirm the running version. Retain the deployment record for the change." }, { "id": "evidence", "title": "Review privileged activity", "text": "Preserve available logs and investigate administrative account activity before the upgrade. Follow Arista’s guidance for signs of exploitation." } ], "affected": [ { "product": "VCO 5.2.x", "range": "Before 5.2.3.18", "fixed_in": [ "5.2.3.18" ] }, { "product": "VCO 6.1.x", "range": "Before 6.1.3.10", "fixed_in": [ "6.1.3.10" ] }, { "product": "VCO 6.4.x", "range": "Before 6.4.2.12", "fixed_in": [ "6.4.2.12" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T20:34:00Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T20:34:00Z", "sources": [ { "title": "Security Advisory 0199", "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199", "publisher": "Arista", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" } ], "changelog": [ { "at": "2026-10-23T20:34:00Z", "text": "Initial local draft. Active exploitation reported by Arista." }, { "at": "2026-10-23T21:03:38Z", "text": "Added the response priority rationale and original disclosure date." } ] }, { "slug": "beyondtrust-bt26-05", "url": "https://www.oktsec.com/radar/beyondtrust-bt26-05", "title": "BeyondTrust Remote Support: exploited appliance flaw", "summary": "BeyondTrust confirms targeted exploitation of Remote Support. Operators of their own appliances must verify that the BT26-05 patch was applied.", "body": "BeyondTrust describes two affected customers in its October 16 update. That scope does not establish broad compromise of every installation. The public advisory says hosted Remote Support was patched by October 9.\n\nPrivileged Remote Access shares affected code and received a precautionary patch, but BeyondTrust did not identify a working exploitation path in PRA. Do not label PRA exploitation as confirmed.", "audience": "Teams operating their own BeyondTrust appliances.", "agent_angle": "Review privileged credentials that an affected remote access appliance could reach, including agent infrastructure.", "kind": "vulnerability", "priority": "act_now", "triage": { "basis": "confirmed_exploitation", "reach": "unauthenticated", "reason": "Remote Support exploitation is confirmed. The appliance can provide access to privileged sessions and credentials." }, "reported_on": "2026-10-15", "cvss": { "score": 9.3, "version": "4.0" }, "topics": [], "vendor": "BeyondTrust", "products": [ "Remote Support", "Privileged Remote Access" ], "cves": [ "CVE-2026-102764" ], "kev": [ { "cve": "CVE-2026-102764", "vendor": "BeyondTrust", "product": "Remote Support", "title": "BeyondTrust Remote Support Authentication Bypass by Spoofing Vulnerability", "description": "BeyondTrust Remote Support contains an authentication bypass by spoofing vulnerability that could allow a remote attacker to perform file operations on the appliance.", "date_added": "2026-10-16", "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.", "federal_due_date": "2026-10-19", "ransomware": "Unknown", "forensic_triage": "Yes" } ], "exploitation": "exploited", "patch": "available", "action": "Verify BT26-05 patch status and investigate unexpected appliance activity.", "checklist": [ { "id": "scope", "title": "Identify deployment and patch state", "text": "Distinguish vendor hosted instances from your own appliances. Verify the BT26-05 patch, not only the product version." }, { "id": "action", "title": "Apply the appliance patch", "text": "Remote Support versions older than 24.3.1 need an upgrade before this patch can be applied. Follow the advisory and confirm installation." }, { "id": "evidence", "title": "Review privileged access", "text": "Preserve off appliance evidence and inspect unexpected sessions, files and credential use. Escalate suspicious activity for incident response." } ], "affected": [], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "BT26-05 security advisory", "url": "https://www.beyondtrust.com/trust-center/security-advisories/bt26-05", "publisher": "BeyondTrust", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" }, { "title": "ARMORY CASTLE investigation and response", "url": "https://www.beyondtrust.com/blog/entry/bt26-05", "publisher": "BeyondTrust", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] }, { "slug": "cisco-expressway-cve-2026-76466", "url": "https://www.oktsec.com/radar/cisco-expressway-cve-2026-76466", "title": "Cisco Expressway: patch clustered deployments", "summary": "Cisco fixed a root command execution flaw in clustered Expressway devices. The advisory reports no known malicious use.", "body": "The flaw requires network access to the database service and possession of the relevant persistent cookies. Cisco lists X15.5.3 and earlier as affected and instructs X14 or older deployments to migrate. There is no vendor workaround.", "audience": "Organizations running vulnerable clustered Expressway-C or Expressway-E.", "agent_angle": "No direct agent exposure is documented. Include affected collaboration infrastructure in the organization’s patch inventory.", "kind": "vulnerability", "priority": "this_week", "triage": { "basis": "critical_fix", "reach": "conditional", "reason": "Critical root execution with a vendor fix, but no known malicious use in the advisory. The affected configuration requires clustering." }, "reported_on": "2026-10-21", "cvss": { "score": 9.8, "version": "3.1" }, "topics": [], "vendor": "Cisco", "products": [ "Expressway-C", "Expressway-E" ], "cves": [ "CVE-2026-76466" ], "kev": [], "exploitation": "none_known", "patch": "available", "action": "Upgrade affected clusters to X15.5.20 or a later fixed release.", "checklist": [ { "id": "scope", "title": "Confirm clustering and version", "text": "Check Expressway-C and Expressway-E appliances and virtual deployments. Identify affected cluster members." }, { "id": "action", "title": "Plan and verify the upgrade", "text": "Apply X15.5.20 or a later fixed release, following Cisco’s migration guidance for older branches." }, { "id": "evidence", "title": "Review service access", "text": "Restrict database service reachability to required peers and inspect unexpected access. Network restrictions do not replace the patch." } ], "affected": [ { "product": "Expressway X15.5.3 and earlier", "range": "Clustered deployments", "fixed_in": [ "X15.5.20" ] }, { "product": "Expressway X14 and earlier", "range": "Clustered deployments", "fixed_in": [ "Migrate to a fixed release" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "Expressway remote code execution advisory", "url": "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t", "publisher": "Cisco", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] }, { "slug": "emudhra-chrome-root-removal", "url": "https://www.oktsec.com/radar/emudhra-chrome-root-removal", "title": "eMudhra: check certificate chains before October 27", "summary": "Chrome plans to remove trust in emSign ECC Root CA - G3. Services using that root need a replacement certificate chain.", "body": "Google announced the Chrome root removal for the morning of October 27, Pacific time. Check the complete chain served by each endpoint, including customer portals and API gateways.\n\nA browser trust change does not automatically update every application trust store. Oktsec recommends validating representative clients and agent tools after certificate replacement. Keep Chrome, Android and other runtime guidance separate.\n\nOracle’s October 21 alert addresses the compromised intermediates through Java and GraalVM updates. Its affected version matrix is separate from Chrome’s deadline. Consult Oracle’s patch availability guidance for each deployed runtime.", "audience": "Service owners whose TLS chain terminates at the affected emSign root.", "agent_angle": "Agents may use trust stores supplied by their runtime or container. Check those separately from Chrome.", "kind": "trust_pki", "priority": "act_now", "triage": { "basis": "deadline", "reach": "conditional", "reason": "Chrome’s October 27 trust removal can interrupt customer connections. Certificate replacement and client testing need time.", "deadline": "2026-10-27" }, "reported_on": "2026-10-21", "topics": [], "vendor": "eMudhra / Google", "products": [ "Chrome", "TLS certificate chains", "Java SE", "GraalVM" ], "cves": [ "CVE-2026-91403" ], "kev": [], "patch": "partial", "action": "Replace affected certificate chains before Chrome’s October 27 trust change.", "checklist": [ { "id": "scope", "title": "Inspect certificate chains", "text": "Identify public endpoints that chain to emSign ECC Root CA – G3. Include certificates supplied by hosting and infrastructure providers." }, { "id": "action", "title": "Replace affected chains", "text": "Arrange replacement before Chrome’s October 27 deadline, in the morning Pacific time. Confirm which chain each endpoint actually serves." }, { "id": "evidence", "title": "Test the clients that use them", "text": "Check Oracle’s CVE-2026-91403 alert for Java and GraalVM, plus the trust stores bundled with containers and AI agent tools. Test real client connections after replacement." } ], "affected": [ { "product": "TLS certificate chain", "range": "Chains terminating at emSign ECC Root CA - G3", "fixed_in": [ "Deploy an alternative trusted chain" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T20:34:00Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T20:34:00Z", "sources": [ { "title": "Chrome and Android response to compromised eMudhra intermediates", "url": "https://blog.google/security/protecting-chrome-and-android-users-from-compromised-emudhra-intermediate-ca-certificates/", "publisher": "Google", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" }, { "title": "Java security alert CVE-2026-91403", "url": "https://www.oracle.com/security-alerts/alert-cve-2026-91403.html", "publisher": "Oracle", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T20:34:00Z", "text": "Priority override: Act now because a dated trust removal can interrupt customer access. No successful attack is inferred from the trust decision." }, { "at": "2026-10-23T21:03:38Z", "text": "Added the response priority rationale and original disclosure date." } ] }, { "slug": "gitlab-cve-2026-110264", "url": "https://www.oktsec.com/radar/gitlab-cve-2026-110264", "title": "GitLab issues an emergency code execution fix", "summary": "A critical regular expression compiler flaw can allow unauthenticated code execution. GitLab recommends upgrading affected installations immediately.", "body": "GitLab rates the flaw CVSS 3.1 10.0. Exploitation depends on specified conditions; the rating does not establish attacks against your installation. The cited advisory does not report active exploitation.\n\nGitLab.com is patched. Dedicated tenants on the internal builds identified in the advisory already have the fix. Operators of their own installations must verify their release against the vendor’s affected ranges.", "audience": "Teams operating GitLab CE or EE on their own infrastructure.", "agent_angle": "Include repository tokens, runner credentials and coding agent integrations in the exposure review.", "kind": "vulnerability", "priority": "this_week", "triage": { "basis": "critical_fix", "reach": "conditional", "reason": "Critical code execution under specific conditions; no exploitation is reported in the cited advisory. Prioritize exposed instances during patch planning." }, "reported_on": "2026-10-21", "cvss": { "score": 10, "version": "3.1" }, "topics": [], "vendor": "GitLab", "products": [ "GitLab CE", "GitLab EE" ], "cves": [ "CVE-2026-110264" ], "kev": [], "exploitation": "none_known", "patch": "available", "action": "Upgrade GitLab to a fixed release and confirm the version serving traffic.", "checklist": [ { "id": "scope", "title": "Locate affected GitLab instances", "text": "Compare deployed CE and EE versions with the advisory. Check the release that is running, not only the package or image configured for deployment." }, { "id": "action", "title": "Apply the emergency update", "text": "Upgrade to the fixed release for your supported branch and verify that each instance is serving the updated version." }, { "id": "evidence", "title": "Record the exposure review", "text": "Review available activity for the period before the update using the vendor guidance. Record findings and telemetry gaps separately from patch completion." } ], "affected": [ { "product": "GitLab CE / EE 7.0–18.11", "range": "7.0 through versions before 18.11.13", "fixed_in": [ "18.11.13" ] }, { "product": "GitLab CE / EE 19.0", "range": "19.0 before 19.0.10", "fixed_in": [ "19.0.10" ] }, { "product": "GitLab CE / EE 19.1", "range": "19.1 before 19.1.9", "fixed_in": [ "19.1.9" ] }, { "product": "GitLab CE / EE 19.2", "range": "19.2 before 19.2.9", "fixed_in": [ "19.2.9" ] }, { "product": "GitLab CE / EE 19.3", "range": "19.3 before 19.3.6", "fixed_in": [ "19.3.6" ] }, { "product": "GitLab CE / EE 19.4", "range": "19.4 before 19.4.3", "fixed_in": [ "19.4.3" ] }, { "product": "GitLab CE / EE 19.5", "range": "19.5 before 19.5.1", "fixed_in": [ "19.5.1" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T20:34:00Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T20:34:00Z", "sources": [ { "title": "GitLab critical patch release", "url": "https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/", "publisher": "GitLab", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" } ], "changelog": [ { "at": "2026-10-23T20:34:00Z", "text": "Priority override: Act now follows the vendor’s immediate upgrade recommendation for unauthenticated RCE, not a claim of observed exploitation." }, { "at": "2026-10-23T21:03:38Z", "text": "Set This week under Radar’s priority rules: critical vendor fix without reported exploitation. Exposed instances still need prompt patch planning." } ] }, { "slug": "netscaler-cve-2026-88771", "url": "https://www.oktsec.com/radar/netscaler-cve-2026-88771", "title": "NetScaler: exploited flaws need patching and investigation", "summary": "Citrix confirms exploitation of two NetScaler flaws. Check appliance versions and preserve evidence of activity before the update.", "body": "Citrix confirms attacks against CVE-2026-88771 and CVE-2026-88772. The first affects default configurations; the second requires DTLS, which is enabled by default on VPN virtual servers. This is an earlier disclosure still requiring action, not a new October 23 vulnerability.", "audience": "Organizations operating NetScaler ADC or Gateway.", "agent_angle": "Check downstream credentials and connectivity used by AI agents behind an affected appliance.", "kind": "vulnerability", "priority": "act_now", "triage": { "basis": "confirmed_exploitation", "reach": "unauthenticated", "reason": "Observed exploitation affects edge infrastructure. CVE-2026-88771 needs no additional feature to be enabled." }, "reported_on": "2026-09-27", "cvss": { "score": 9.5, "version": "4.0" }, "topics": [], "vendor": "Citrix", "products": [ "NetScaler ADC", "NetScaler Gateway" ], "cves": [ "CVE-2026-88771", "CVE-2026-88772" ], "kev": [ { "cve": "CVE-2026-88771", "vendor": "Citrix", "product": "NetScaler", "title": "Citrix NetScaler Improper Input Validation Vulnerability", "description": "Citrix NetScaler ADC and NetScaler Gateway contain an improper input validation vulnerability that could allow an unauthenticated attacker to execute arbitrary commands.", "date_added": "2026-09-27", "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.", "federal_due_date": "2026-09-30", "ransomware": "Unknown", "forensic_triage": "Yes" }, { "cve": "CVE-2026-88772", "vendor": "Citrix", "product": "NetScaler", "title": "Citrix NetScaler Improper Restriction of Operations within the Bounds of a Memory Buffer Vulnerability", "description": "Citrix NetScaler ADC and NetScaler Gateway contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for remote code execution or denial of service", "date_added": "2026-09-27", "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.", "federal_due_date": "2026-09-30", "ransomware": "Unknown", "forensic_triage": "Yes" } ], "exploitation": "exploited", "patch": "available", "action": "Install the vendor fixes and investigate unexpected access or persistence.", "checklist": [ { "id": "scope", "title": "Find affected appliances", "text": "Inventory ADC and Gateway deployments, including high availability peers. Match each build and configuration to CTX697096." }, { "id": "action", "title": "Patch and verify", "text": "Use the fixed branch or supported successor. Confirm the running build on every appliance after the change." }, { "id": "evidence", "title": "Investigate prior access", "text": "Preserve logs externally and review unexpected accounts, files and connections. Patching does not remove an existing intruder." } ], "affected": [ { "product": "ADC / Gateway 14.1", "range": "Before 14.1-73.37", "fixed_in": [ "14.1-73.37" ] }, { "product": "ADC / Gateway 13.1", "range": "Before 13.1-64.23", "fixed_in": [ "13.1-64.23" ] }, { "product": "14.1 FIPS", "range": "Before the listed fixed build", "fixed_in": [ "14.1-73.37 FIPS" ] }, { "product": "13.1 FIPS / NDcPP", "range": "Before the listed fixed build", "fixed_in": [ "13.1.37.279" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "NetScaler security bulletin CTX697096", "url": "https://support.citrix.com/external/article/CTX697096", "publisher": "Citrix", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] }, { "slug": "nodejs-brotli-cve-2026-111497", "url": "https://www.oktsec.com/radar/nodejs-brotli-cve-2026-111497", "title": "Node2Shell: update runtimes that decode untrusted Brotli", "summary": "A Node.js decoder flaw can allow code execution when an application decompresses attacker supplied Brotli data. Imperva demonstrated the impact in specific Linux arm64 configurations.", "body": "The defect is in Node.js, not Express itself. Request middleware and consumed HTTP responses can expose the decoder. A bare HTTP server does not decompress an incoming body merely because it receives it.\n\nImperva demonstrated code execution on Node.js 24.22.0 in Linux arm64 tests and rejection of the same input on 24.22.1. This is research evidence, not confirmation of attacks against customers.", "audience": "Node.js applications that decode untrusted Brotli requests or responses.", "agent_angle": "Include MCP servers and agent tools that fetch compressed responses or parse incoming request bodies.", "kind": "vulnerability", "priority": "act_now", "triage": { "basis": "public_exploit", "reach": "conditional", "reason": "A working research demonstration reaches code execution. Exposure depends on untrusted data reaching the bundled Brotli decoder." }, "reported_on": "2026-10-21", "topics": [ "ai_agents" ], "vendor": "Node.js", "products": [ "Node.js", "Express", "body-parser" ], "cves": [ "CVE-2026-111497" ], "kev": [], "exploitation": "poc_public", "patch": "available", "action": "Update the deployed Node.js runtime and identify paths that decode untrusted data.", "checklist": [ { "id": "scope", "title": "Find deployed runtimes", "text": "Inspect the Node.js binary inside running containers and services. Trace untrusted compressed input to fetch or configured request parsers." }, { "id": "action", "title": "Replace affected runtimes", "text": "Deploy the fixed release for each supported branch and rebuild images that bundle Node.js. Confirm the running version." }, { "id": "evidence", "title": "Review relevant telemetry", "text": "Investigate unusual process failures alongside request and host activity. Decoder errors alone do not prove exploitation." } ], "affected": [ { "product": "Node.js 22.x", "range": "Before 22.23.4", "fixed_in": [ "22.23.4" ] }, { "product": "Node.js 24.x", "range": "Before 24.22.1", "fixed_in": [ "24.22.1" ] }, { "product": "Node.js 26.x", "range": "Before 26.12.1", "fixed_in": [ "26.12.1" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "October Node.js security releases", "url": "https://nodejs.org/en/blog/vulnerability/october-2026-security-releases", "publisher": "Node.js", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" }, { "title": "Node2Shell research demonstration", "url": "https://www.imperva.com/blog/node2shell-from-brotli-data-to-remote-code-execution/", "publisher": "Imperva", "kind": "research", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] }, { "slug": "php2shell", "url": "https://www.oktsec.com/radar/php2shell", "title": "PHP2Shell: investigate from October 17", "summary": "AWS observed exploitation attempts before disclosure. Patch exposed PHP servers and investigate the activity that preceded the update.", "body": "AWS dates the earliest observed attempt to October 17. Its report does not establish whether those attempts succeeded against real systems. A patched server still needs a review of earlier activity. Record gaps in telemetry.\n\nThe versions below fix the original two CVEs. PHP’s October 23 follow up, CVE-2026-115560, concerns an unusual session configuration and has a separate fix pending. Follow the vendor’s upload progress mitigation guidance while that fix is pending.", "audience": "Teams running PHP applications that accept web requests.", "agent_angle": "Check credentials and internal tools accessible from affected applications, including those used by AI agents.", "kind": "vulnerability", "priority": "act_now", "triage": { "basis": "observed_attempts", "reach": "unauthenticated", "reason": "AWS observed attempts before disclosure. Review web exposure and activity from October 17 while applying PHP’s follow up guidance." }, "reported_on": "2026-10-21", "topics": [], "vendor": "PHP", "products": [ "PHP" ], "cves": [ "CVE-2026-109618", "CVE-2026-109619", "CVE-2026-115560" ], "kev": [], "exploitation": "attempts_observed", "patch": "partial", "action": "Patch PHP, preserve logs and review server activity from at least October 17.", "checklist": [ { "id": "scope", "title": "Identify exposed PHP", "text": "Compare the deployed PHP version with the fixed releases. Include web applications, containers and servers managed by a hosting provider." }, { "id": "action", "title": "Apply the vendor guidance", "text": "Install the applicable fixed release and check PHP’s separate session upload progress follow up. Confirm the version actually serving requests." }, { "id": "evidence", "title": "Investigate earlier activity", "text": "Preserve and review host activity from at least October 17, including credentials accessible to the PHP process. Record any gaps in the logs." } ], "affected": [ { "product": "PHP 8.5", "range": "Before 8.5.12", "fixed_in": [ "8.5.12" ] }, { "product": "PHP 8.4", "range": "Before 8.4.27", "fixed_in": [ "8.4.27" ] }, { "product": "PHP 8.3", "range": "Before 8.3.36", "fixed_in": [ "8.3.36" ] }, { "product": "PHP 8.2", "range": "Before 8.2.35", "fixed_in": [ "8.2.35" ] } ], "verification": "vendor_confirmed", "published_at": "2026-10-23T20:34:00Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T20:34:00Z", "sources": [ { "title": "PHP critical security advisory", "url": "https://www.php.net/archive/2026.php#2026-10-21-5", "publisher": "PHP", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" }, { "title": "PHP2Shell observations in MadPot", "url": "https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/", "publisher": "AWS", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" }, { "title": "Session upload progress follow up", "url": "https://www.php.net/archive/2026.php#2026-10-23-1", "publisher": "PHP", "kind": "vendor", "checked_at": "2026-10-23T20:34:00Z" } ], "changelog": [ { "at": "2026-10-23T20:34:00Z", "text": "Act now: public exploits and observed attempts against web infrastructure. Attempts are not labeled confirmed compromise." }, { "at": "2026-10-23T21:03:38Z", "text": "Clarified that the original fixes do not close the separate October 23 session issue; further vendor action remains necessary." } ] }, { "slug": "pingcap-october-2026-api-keys", "url": "https://www.oktsec.com/radar/pingcap-october-2026-api-keys", "title": "PingCAP: replace management API keys as a precaution", "summary": "PingCAP confirms an internal systems incident and exported customer records. Its customer guidance calls for replacing active TiDB Cloud management keys.", "body": "PingCAP reports unauthorized access between September 9 and October 7. It found no evidence that data stored in TiDB was impacted. Exported records included account and business information; the API key values were encrypted.\n\nThe October 20 guidance says there is no evidence of key decryption or use, but asks customers to rotate active management keys without waiting for individual notification. Radar’s Act now priority reflects that precaution, not a claim that plaintext keys were stolen.", "audience": "TiDB Cloud organization owners and teams using management API keys.", "agent_angle": "Update management credentials in automation and AI agent tools, then confirm old keys are revoked.", "kind": "platform_breach", "priority": "act_now", "triage": { "basis": "vendor_precaution", "reach": "provider_access", "reason": "PingCAP requests immediate preventive rotation. Exported keys were encrypted; decryption or misuse has not been established." }, "reported_on": "2026-10-19", "topics": [ "cloud_secrets", "ai_agents" ], "vendor": "PingCAP", "products": [ "TiDB Cloud" ], "cves": [], "kev": [], "patch": "partial", "action": "Replace active management keys and verify unexpected account requests.", "checklist": [ { "id": "scope", "title": "Inventory management keys", "text": "Find active TiDB Cloud management API keys and their dependent applications in each organization." }, { "id": "action", "title": "Replace keys safely", "text": "Without suspected misuse, replace keys, verify dependent applications and revoke the old keys promptly. For suspected misuse, revoke immediately and contact PingCAP." }, { "id": "evidence", "title": "Review activity and requests", "text": "Inspect available account logs. Verify unexpected payment, password or account requests through a known channel." } ], "affected": [], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "October incident report", "url": "https://www.pingcap.com/trust-hub/security/security-update-october-2026/", "publisher": "PingCAP", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" }, { "title": "Customer actions and API key replacement", "url": "https://www.pingcap.com/trust-hub/security/customer-actions-october-2026/", "publisher": "PingCAP", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] }, { "slug": "railway-october-2026-secrets", "url": "https://www.oktsec.com/radar/railway-october-2026-secrets", "title": "Railway: replace stored secrets after the platform incident", "summary": "Railway’s preliminary report confirms that some encrypted environment variables were decrypted. It recommends replacing sensitive variables stored before October 21.", "body": "The report limits potential environment variable compromise to a subset of workspaces. Broad provider revocations do not prove that each revoked key was stolen. Railway says the investigation is ongoing; service restoration is not evidence that customers have completed credential replacement.", "audience": "Teams that stored sensitive environment variables on Railway before October 21.", "agent_angle": "Include model API keys, deployment tokens and credentials used by AI agent tools.", "kind": "platform_breach", "priority": "act_now", "triage": { "basis": "credentials_exposed", "reach": "provider_access", "reason": "The provider confirms decrypted secrets in a subset of workspaces. Credential replacement remains necessary after service restoration." }, "reported_on": "2026-10-21", "topics": [ "ai_agents", "cloud_secrets" ], "vendor": "Railway", "products": [ "Railway" ], "cves": [], "kev": [], "patch": "partial", "action": "Replace reachable secrets, revoke old access and review provider activity.", "checklist": [ { "id": "scope", "title": "Map stored secrets", "text": "List sensitive variables present before October 21 and the external systems they authorized." }, { "id": "action", "title": "Replace and revoke", "text": "Coordinate replacements with application owners, then confirm old credentials are revoked at each issuer. Revoke suspected misuse immediately." }, { "id": "evidence", "title": "Inspect downstream use", "text": "Review provider audit logs, repository access and model usage. Investigate unexpected spend or access even if builds now run normally." } ], "affected": [], "verification": "vendor_confirmed", "published_at": "2026-10-23T21:03:38Z", "updated_at": "2026-10-23T21:03:38Z", "last_verified_at": "2026-10-23T21:03:38Z", "sources": [ { "title": "Preliminary report: October security incident", "url": "https://blog.railway.com/p/preliminary-report-october-security-incident", "publisher": "Railway", "kind": "vendor", "checked_at": "2026-10-23T21:03:38Z" } ], "changelog": [ { "at": "2026-10-23T21:03:38Z", "text": "Added to the local collection after reviewing original sources. Disclosure date is shown separately from Radar coverage." } ] } ] }