
Digtool: A Virtualization-Based Framework for Detecting Kernel Vulnerabilities usenix.org/conference/usenix…

Security Researcher. Usenix 2017 ,MSRC top 100 2016/2017/2018. Opinions are my own.

Digtool: A Virtualization-Based Framework for Detecting Kernel Vulnerabilities usenix.org/conference/usenix…

MissionControlAggregator.dll (AggregatorHost/DiagTrack) counts if Claude, Codex, Cursor, Copilot, or Antigravity ran. It reports cohort slots and a time window, not understand why MS collect them.

The Mythos model is being hyped so intensely—yet why is it that anthropic only uncover 10 Windows vulnerabilities this year?And none of these were exclusive discoveries (external researchers don’t have access to a model of Mythos’s caliber).



also support show external ID and CVE number.

If you’re like me and have grown tired of the clunky portal system used by MSRC, try this browser extension —it’ll make your life easier.. github.com/tinysec/msrc-ext , Allowing cases to be opened in a new tab without requiring a re-login(I simply cannot fathom the design choices behind MSRC )

Another Patch Tuesday—judging by the number of CVEs and the valueable changes, it seems the peak has passed. This month i got CVE-2026-95938,CVE-2026-119933,CVE-2026-119872,CVE-2026-119383,CVE-2026-112984,CVE-2026-112969,CVE-2026-113817,CVE-2026-119856😂

#patchdiff i think it's CVE-2026-96923 , and also it's auto analyzed and generate poc by AI.

Sorry, I assumed that Slack channels were open for anyone to join by default—I didn't realize an invitation was required. join.slack.com/t/patchdiff/s… current this workspace is empty
To my surprise, the subdomain patchdiff.slack.com is available , so i create this workspace.

To my surprise, the subdomain patchdiff.slack.com is available , so i create this workspace.

finally at Oct. CVE-2026-69798,CVE-2026-85909,CVE-2026-70295,CVE-2026-83518,CVE-2026-102188,CVE-2026-96844,CVE-2026-83776,CVE-2026-83639
get CVE-2026-70295,CVE-2026-83518,CVE-2026-85909,CVE-2026-102188 from this patch thuesday.

As I’ve mentioned, MSRC is constantly revising the rules that external researchers must follow; yet, what truly needs to change is their attitude toward these researchers.
Have read @TinySecEx's posts about @msftsecresponse, well, I'd like to share my own.. I don’t think they treated me in some kinda of "disrespect", that's the good part (& thankfully). But I have (and hate) to say that their recent handling of some cases has been frustrating — a lot of self-contradictory "explanations" given back and forth when a case was wrongly triaged. For the case I’m currently dealing with, I finally found some time this week to review all the technical details again. After gathering all the technical facts, at this point, I honestly don’t even know if they understood what they were doing when they made that "bold" "Won’t Fix" decision.. I am still trying and waiting for more "explanations", I sent the last email (about why their "reasons" are self-contradictory and why it poses risks to Office users if they refuse to patch the RCE bug) last week and pinged them again this Monday, but nobody has bothered to reply yet. Either way, once this plays out, I think I have done the best part of mine as an external researcher and I’ll decide if I need to write a post explaining some Office Security basics — like "why Microsoft needs to patch that (damn) Office bug" — for the greater good.

What MSRC needs to change most is not its rules, but rather how it truly respects external researchers—and I mean genuine respect, not just lip service. These researchers are not your enemies!
Security researchers play an essential role in helping Microsoft protect customers, and we appreciate the time and expertise that goes into every vulnerability report. Many researchers already provide the detailed, actionable reports our teams need to reproduce and assess vulnerabilities quickly. Starting October 20, Microsoft bounty programs will use Complete and Not Complete report assessments to make those expectations clearer and help provide more predictable bounty awards. Learn what makes a report Complete and how to prepare your next submission in our blog: aka.ms/complete-report-blog

get CVE-2026-70295,CVE-2026-83518,CVE-2026-85909,CVE-2026-102188 from this patch thuesday.