// Intelligence Brief · Week 43
10 items that need action
2026-10-19 → 2026-10-25 UTC · 10 items selected
ACTION NEEDED
VERIFY_EXPOSURE
WHAT CHANGEDCVE-2026-111943: eMudhra intermediate CA key recovery in AWS trust bundles. Source event: 2026-10-25T03:07:57+00:00. RSS discovery: 2026-10-25T04:42:10.925585+00:00.
WHY IT MATTERSThe captured feed identifies CVE-2026-111943. Check exposure against the affected product and versions; detailed remediation evidence is unavailable.
WHAT TO DOCheck your inventory for the product and affected versions named in this advisory. Remediation details were not captured; consult the vendor bulletin before changing configuration or applying a fix. Remediation: see bulletin https://aws.amazon.com/security/security-bulletins/2026-150-aws/ (retrieval attempted 2026-10-25T04:43:54.995Z; RSS discovery 2026-10-25T04:42:10.925585+00:00).
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
VERIFY_ONLY
WHAT CHANGEDCloudflare is deploying two new WAF rules on 25 October 2026 for CVE-2026-111497: rule ca706f3c matches requests with Content-Encoding: br header, rule 402fe5bb matches requests to /_next/image endpoint. Both rules default to Log action (non-blocking) in the Cloudflare Managed Ruleset.
WHY IT MATTERSIf you have a ruleset-level action override set to Block, these new rules will block matching traffic immediately on deployment despite their Log default, potentially blocking legitimate Brotli-encoded requests and Next.js image optimization traffic. Without reviewing overrides first, this creates unintended false positives.
WHAT TO DOCheck your Cloudflare WAF ruleset overrides before 25 October 2026. If you have a ruleset-level Block override, configure rule-specific overrides for ca706f3c and 402fe5bb to use Log action, then review analytics for matches before switching to Block.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
MIGRATE
WHAT CHANGEDAzure Foundry assigned retirement dates to 10 GA models: FLUX-1.1-pro and FLUX.1-Kontext-pro retire 2027-01-05; FLUX.2-flex, FLUX.2-pro retire 2027-01-20; Llama-3.3-70B-Instruct, grok-4, grok-code-fast-1, Llama-4-Scout-17B-16E-Instruct retire 2027-01-31; Codestral-2501 retires 2027-02-15; Llama-4-Maverick-17B-128E-Instruct-FP8 retires 2026-11-19. The gpt-realtime-2 preview retirement date moved from 2026-05-06 to 2027-01-20.
WHY IT MATTERSApplications using any of these 10 models will stop working on the stated dates unless migrated to replacement models. The earliest cutoff is 26 days away (2026-11-19 for Llama-4-Maverick-17B-128E-Instruct-FP8).
WHAT TO DOGrep your codebase and deployment configs for these 11 model identifiers. For each match, schedule migration to a supported replacement before its retirement date, starting with Llama-4-Maverick-17B-128E-Instruct-FP8 by 2026-11-19.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
PATCH_NOW
WHAT CHANGEDGitHub published CVE-2026-53995 on 20 October 2026, a high-severity path traversal vulnerability in mlflow's FileStore trace ID handling. The flaw allows arbitrary file writes. Patched in mlflow 3.17.2.
WHY IT MATTERSAn attacker who can control trace IDs can write files anywhere the mlflow process has permissions, potentially overwriting application code, configuration, or credentials. This affects any deployment using mlflow's FileStore backend for trace logging.
WHAT TO DOUpgrade to mlflow 3.17.2 or later. If you use mlflow for experiment tracking or model registry, check whether FileStore is your trace backend and prioritize the update if so.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
PATCH_NOW
WHAT CHANGEDCVE-2026-112940 published 23 October 2026 for filelock (Python). ReadWriteLock reopens the SQLite lock database by name, allowing an attacker who can plant a symlink or journal file to cause the victim process to overwrite or unlink its own files. First patched version: 4.2.1.
WHY IT MATTERSfilelock is a common dependency in Python services. Any process using ReadWriteLock on a filesystem where an attacker can write (shared temp directories, user-writable paths) can be forced to corrupt or delete its own files, leading to data loss or denial of service.
WHAT TO DOCheck whether your services depend on filelock (any version before 4.2.1) and use ReadWriteLock. If so, upgrade to filelock 4.2.1 or later. Verify that lock database paths are not in attacker-writable directories.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
PATCH_NOW
WHAT CHANGEDPython added a denylist to the ssl module that automatically rejects known compromised certificates regardless of SSLContext policy configuration. The change is tracked as CVE-2026-115557 and implemented in cpython pull request 160042.
WHY IT MATTERSAny Python service making TLS connections will now reject connections using the denylisted certificates even if certificate revocation checking is disabled or misconfigured, preventing connections to potentially compromised endpoints that were previously accepted.
WHAT TO DOVerify which Python versions contain this fix by checking CVE-2026-115557, then update Python runtimes in production to a patched version. Test that legitimate services still connect after the update.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
VERIFY_EXPOSURE
WHAT CHANGEDCVE-2026-109618 and CVE-2026-109619 allow unauthenticated remote code execution on vulnerable PHP versions. Fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. No fix exists for PHP 8.1 or earlier. Apigee developer portals running Drupal are affected; other Apigee products are not.
WHY IT MATTERSUnauthenticated attackers can execute arbitrary code on exposed Apigee developer portals. Portals running PHP 8.1 or earlier have no patch available and remain vulnerable.
WHAT TO DOIf you operate an Apigee developer portal, check your PHP version. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-072 Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-072. The full article could not be retrieved (attempted 2026-10-25T04:43:43.009Z); this item uses the feed entry only.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
VERIFY_EXPOSURE
WHAT CHANGEDCVE-2026-114625, an SQL injection vulnerability in Arista VeloCloud Orchestrator, was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-24 with a due date of 2026-10-26. The vulnerability is confirmed to be exploited in the wild.
WHY IT MATTERSVeloCloud Orchestrator is the control plane for SD-WAN deployments. SQL injection at this layer gives attackers access to network configuration, routing policies, and potentially credentials for managed edge devices. Active exploitation means threat actors already have working tooling.
WHAT TO DOVerify whether you run VeloCloud Orchestrator and check your version against vendor guidance. Apply vendor mitigations by 2026-10-26 to meet BOD 26-04 compliance requirements, or discontinue use if mitigations are unavailable. Federal agencies must also follow CISA's Forensics Triage Requirements.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
MITIGATE
WHAT CHANGEDCVE-2026-110447, an OS command injection vulnerability in Collabora Online Built-in CODE Server, was added to CISA's Known Exploited Vulnerabilities catalog on 2026-10-24 with a remediation deadline of 2026-10-26.
WHY IT MATTERSActive exploitation is confirmed. Command injection vulnerabilities allow attackers to execute arbitrary system commands on the server, potentially leading to full system compromise of collaboration infrastructure.
WHAT TO DOApply vendor mitigations by 2026-10-26 per CISA BOD 26-04 requirements. If you run Collabora Online, check vendor security advisories for patches or workarounds. Federal agencies and BOD-covered entities must remediate or discontinue use by the due date.
Full item and evidence ↗ · Primary source ↗
ACTION NEEDED
PATCH_NOW
WHAT CHANGEDOn 2026-10-17, private keys for eight eMudhra subordinate CA certificates (including those cross-signed by AAA Certificate Services) were compromised due to weak entropy. Google revoked trust in these CAs across managed infrastructure. The compromise affects Google Cloud CLI, Cloud Shell, Container-Optimized OS, Compute Engine, GKE, Vertex AI, Colab Enterprise, App Engine, Cloud Run, Cloud Functions, Firebase services, Cloud SQL, AlloyDB, Cloud Firestore, Cloud Monitoring, Confidential Space, and Google Distributed Cloud.
WHY IT MATTERSAttackers with network access can reconstruct the compromised private keys to forge trusted TLS certificates and perform Man-in-the-Middle attacks against any TLS clients, containers, or SDKs still trusting these CAs. While Google has mitigated managed environments and reports no exploitation, self-managed operating systems, custom container images, and local CLI installations remain vulnerable until trust stores are updated.
WHAT TO DOUpdate trust stores in self-managed environments: RHEL (follow RHSB-2026-012), Debian (update ca-certificates per Bug 1151446), Ubuntu (follow USN-8944-1), Windows (install latest updates), Container-Optimized OS (upgrade nodes or apply cos_ca_cert_mitigation tool). Update gcloud CLI to latest release. For managed services, monitor product documentation for service-specific rollout details.
Full item and evidence ↗ · Primary source ↗
What the week cost
16runs
$3.5519model cost
40sources watched
0corrections
Printed because they are checkable. No item published this week has been found wrong. That is not a claim of accuracy —
how precision is counted.
RADAR watches 40 sources every twelve hours (scheduled runs often start hours late) and writes up only
what changed materially. Get it weekly or daily by email —
or take the feed, which is free and has
terms that say so.