Quiet morning on the AI side — the weekend's Langflow and LangSmith fixes already shipped here, and no new advisories hit the local runtimes or frameworks over Saturday and Sunday. The one item worth acting on is on the .NET side, and the weekend digests skipped past it: a CVSS 10.0 authentication bypass in CoreWCF's SAML token validation (CVE-2026-54782) that lets a forged token impersonate any principal. A moderate secrets-directory traversal in pydantic-settings rounds out a thin Monday.

Worth your morning

CoreWCF (CVE-2026-54782). The SAML 1.1 / 2.0 token path in CoreWCF — the community port of WCF onto .NET Core that a lot of shops use to keep legacy SOAP services running — does not properly validate token signatures, so a forged token is accepted as genuine. Where authorization keys off SAML claims, that means impersonating any principal, up to and including an administrator. It's a signature-validation step that runs and accepts a signature it never actually verifies, which is where the clean 10.0 comes from. Two ranges are affected — everything below 1.8.1, plus 1.9.0 — and the fixes are 1.8.1 for the 1.8.x line and 1.9.1 for 1.9.x. If you run CoreWCF anywhere that answers SOAP requests, patch today and treat SAML-based auth on it as bypassable until you have.

pydantic-settings (GHSA-4xgf-cpjx-pc3j). The SecretsSettingsSource — the loader that reads secrets out of a directory, the way Docker and Kubernetes secret mounts present them — could be steered through symlinks to read files outside that directory, and the documented size cap could be slipped at the same time. Moderate, 5.3, fixed in 2.14.2. Relevant because pydantic-settings sits under a large share of Python AI services for config and secret loading; if yours pulls secrets from a directory it doesn't fully control, upgrade.