Skip to content
All tags

#microsoft

7 posts

Model Card: Microsoft Mage-VL-Cowork

Microsoft Mage-VL-Cowork (HF ID `microsoft/Mage-VL-Cowork`): published to HuggingFace 2026-10-30, 4B parameters, 32,768-token active context (architecture supports up to 262,144), Apache-2.0, no official paid API. OSWorld-Verified: 66.0%, the best score at the 4B scale, ahead of the 27B Qwen3.6-27B (63.9%), the 72B OpenCUA-72B (44.9%), and Claude Sonnet 4.5 (62.9%) even though Sonnet got double the step budget. A single policy routes between screenshot-based GUI actions (`computer_use`) and `bash` terminal execution on its own, with no external router. Online Hybrid RL (GRPO) adds roughly 10pp over plain Hybrid SFT while cutting model calls by 13% and output tokens by 25.4%. Microsoft's own card says it should only run inside an isolated sandbox or VM, never with real credentials or local filesystem access.

Pricing Watch: Microsoft Foundry's Retirement Clock Runs on Its Own Schedule

Microsoft Foundry's model retirement schedule doesn't track the vendor's own clock. Claude Haiku 4.5 is scheduled to retire on Foundry on 2026-11-15 (two weeks out, with no replacement listed), even though Anthropic's own Claude API, AWS, and Google Cloud still mark it Active. The reverse happened with Mistral Medium 3 (retired on Mistral's own platform 2026-08-31) and Ministral 3B (retired 2025-12-31): Foundry kept both at GA until 2026-12-09, 100 and 343 days after the vendor pulled the plug. Anthropic's own docs say Foundry "follows the Claude API lifecycle schedule," but the actual dates don't match.

How to Write a Bug Report That Earns the Full Reward: Quality Multipliers, a One-Page Template, and Expected Value

Google multiplies the reward by 0.8, 1 or 1.2 depending on report quality across seven dimensions, and only counts what you provided before triage; later additions usually do not change it. Write to a one-page template (title, summary, preconditions, steps, impact, fix suggestion), then estimate hourly expected value as probability x amount / hours. A bigger ceiling can still lose to a small payout once the odds are low enough. Only Resolved is guaranteed to pay; duplicates and invalid reports are common. Every probability and hour count in this post is an assumption, not a statistic.

Bug Bounty Payout Map: What Google, Hyper-V, Meta TEE, Apple and Mozilla Pay For

Read payouts with their product, category, threat scenario and evidence requirements; program ceilings and quality rules are not interchangeable.

A Hyper-V Escape Case Study: CVE-2021-28476, From a Guest's Packet to a Host Crash

CVE-2021-28476 is a bug in Hyper-V's virtual network switch driver: a guest VM sends a crafted request, the host code follows an address inside it without checking, and the host crashes. Akamai claims two scenarios, a crash and code execution, but the public PoC only shows the crash; code execution was not publicly demonstrated. CVSS 9.9, patched May 2021. On the bounty table, what was publicly shown maps to the DoS cell (up to $15,000); the L1 guest-escape cell tops out at $250,000 and needs a working RCE exploit, but without an exploit that cell still has $200,000, $100,000 and $50,000 rows.

Azure Container Apps Sandboxes

The cloud deep dive post (order 14) of the Sandbox Series. Azure Container Apps Sandboxes architecture, snapshot and state management, lifecycle policy, security boundaries, and trade-offs with other providers, plus Azure ecosystem integration advantages.

GraphRAG: Structuring Knowledge as a Graph for Relationship-Based Reasoning

Vector search finds similarity; graph search traverses relationships. When a question requires reasoning across multiple entities — crag → route → sender → grade distribution — GraphRAG outperforms standard RAG.