Field Notes — Week of July 26, 2026
A short, opinionated digest of what actually mattered this week across cloud, security, AI, and automation — and what it means if you run real systems.
Security: A fourth SharePoint RCE, and a public PoC that weaponized itself in hours
The on-prem SharePoint bleeding didn’t stop with July’s Patch Tuesday. CVE-2026-50522, a critical unsafe-deserialization RCE rated CVSS 9.8, went from a public proof-of-concept dropped July 20 to active exploitation within hours, per WatchTowr and multiple trackers. It’s unauthenticated and network-reachable, and it’s the fourth SharePoint Server flaw in this attack wave to see real-world exploitation — after CVE-2026-56164 and CVE-2026-58644.
The nasty part isn’t the code execution, it’s the follow-through: attackers are pulling SharePoint ASP.NET machine keys with a single request and using them to mint forged auth tokens for durable, patch-surviving access. This is the same ToolShell persistence pattern CISA flagged earlier in the month, now running on autopilot behind a released exploit.
The take: Patching is necessary and insufficient. If your on-prem SharePoint was reachable any time after July 20, assume the machine keys are gone — patch, then rotate the ASP.NET machine keys, then restart IIS, in that order. A patch alone does not evict an attacker who already holds your keys; it just closes the door behind them. Hunt for anomalous __VIEWSTATE traffic and unexpected token issuance back to at least the 20th before you call it clean.
Cloud: AWS quietly removes two migration frictions
No summit keynote this week — but two “boring” launches take real friction out of migrations. First, S3 now supports same-day transitions to Standard-IA and One Zone-IA, dropping the old 30-day minimum in S3 Standard. For log analytics, backups, and compliance data that goes cold within hours, that’s up to ~40% lower storage cost you previously had to wait a month to capture. Second, Amazon Cognito now imports users with password hashes in CSV imports — so a lift-and-shift from a legacy identity store no longer forces every user through a reset on first sign-in.
The take: These are the unglamorous items that decide whether a migration lands. The Cognito change removes the single most common reason IAM cutovers stall — you can now cut over without a mass password-reset event and the support tickets that follow. On S3, revisit lifecycle policies you wrote around the 30-day floor; there’s idle spend sitting in Standard that can move to IA on day one. Verify your source system’s hash algorithm is one Cognito accepts before you plan the cutover.
AI: OpenAI’s GPT-5.6 family lands on Bedrock, and agent protocols converge
OpenAI’s GPT-5.6 — Sol, Terra, and Luna — is now generally available on Amazon Bedrock, spanning flagship reasoning (Sol), balanced (Terra), and fast/cost-efficient (Luna) tiers, all served through the Responses API on Bedrock’s inference stack. In parallel, AWS published a walkthrough of open agent protocols — MCP, A2A, UTCP, AG-UI, and x402 — interoperating through the Strands Agents SDK, a sign the interop layer under enterprise agents is standardizing rather than fragmenting.
The take: Frontier models arriving same-era on a hyperscaler’s managed API is the pilot-to-production shortcut — same IAM, same VPC endpoints, same logging you already govern, so you skip a separate vendor security review. Pick the tier per task (don’t route everything to Sol; Luna handles most classification and extraction for a fraction of the cost). And treat the protocol convergence as permission to design for portability now — build against MCP/A2A rather than one vendor’s proprietary agent glue.
Automation: agent-native tooling moves into the build-and-deploy loop
AWS is pushing coding agents deeper into the deployment path. A new one-click Lambda setup prompt configures agents (Claude Code, Kiro, Cursor, Copilot, Codex, and others) with serverless best practices and the Serverless MCP server from the first prompt, and the Agent Toolkit for AWS gives agents current AWS knowledge plus scoped resource access. AWS also shipped self-managed Lambda code storage, letting functions reference source directly from your own S3 buckets with no intermediate copy step.
The take: Agents writing and shipping infrastructure is now the default workflow, not an experiment — which means agent-generated IaC needs the same review gates, least-privilege roles, and change controls as human commits. The Agent Toolkit’s scoped access is the right instinct; use it. Don’t let “one-click” quietly become one-click-to-prod without a plan or approval step in between.
ZelMor LLC helps organizations and consultancies with cloud architecture, AI enablement, security & IAM, and automation. If any of the above is a live question for your team, start a conversation.