.-. .-. (: `--------------------' :) ) intel brief // #13 ( (: .--------------------. :) `-' `-'
- gVisor device-cgroup confinement + filestore cleanup -- Google's user-space kernel quietly bolted the sandbox into a device cgroup and patched a missing filestore cleanup path in the same stretch (heads e45d53c7, ab5f509c). When a sandbox maintainer plugs a descriptor/file lifecycle leak without a bulletin, assume somebody worked out how to hold that handle open across container teardown. Worth a 10-minute diff [google/gvisor].
- Apache HTTP/2 RCE, CVE-2026-119618 -- Wordfence flagged it as critical and remote-code-execution capable; every WordPress host riding Apache front-ends is downstream of whether their provider actually patched. 'Confirm your host has applied the fix' is vendor-speak for 'we have no idea how many boxes are still naked' [Ram Gall / Wordfence].
- CSP allowlists turned into credential exfil pipes -- @albinowax showed that an allowlisted domain serving JSONP, uploads, or open redirects turns blocked XSS right back into token theft ('Blind trust'). Vendors still pitch CSP like a magic seatbelt; on most prod targets it's a pre-approved exfil list [James Kettle / @albinowax].
- WordPress plugin flood: 497 vulns in one week -- Wordfence's weekly report tallies 497 vulnerabilities across 312 plugins and one theme from 218 researchers. Sheer disclosure volume means half of these will never get patched -- pick your targets accordingly [Ram Gall / Wordfence].
- Brotli shared-dictionary state loss on serialized parse failure -- commit 6a14c079 fixes a decoder that drops dictionary state mid-stream, plus a mutex bolted onto BrotliInputStream for concurrent decompression. State-machine resets on error paths are classic memory-corruption breeding ground [google/brotli].
- Git unborn HEAD symref escape, CVE-2026-113408 -- @xssdoctor shipped a loopback protocol-v2 smart-HTTP harness proving git clients swallow an unsafe unborn HEAD symref (
symref -> path escape outside .git). Clean, inert oracle you can run locally in five minutes [xssdoctor/git-cve-2026-113408-poc]. - 'Negative-day' patch hunting goes tooling-grade -- @vitorfhc updated
vdet, a detector that watches major OSS projects for silent security fixes shipped before any CVE exists and then checks whether the fix is actually exploitable. A direct pre-CVE pipeline -- point it at gVisor and see what lights up [vitorfhc/vdet]. - Cloud hacking threat models on the air -- Critical Thinking episode 200 with Nick Copi walks cloud attack scope and how providers and attackers both abuse the same service primitives. Good background noise while you diff sandbox commits [Critical Thinking Podcast].
.-. .-. (: `----------------------' :) ) possibilities // #13 ( (: .----------------------. :) `-' `-'
- Diff gVisor's filestore cleanup for cross-teardown handle retention -- pull heads e45d53c7 and ab5f509c, trace which filestore/descriptor paths lacked cleanup, and try holding an fd across sandbox teardown from a half-dead container to keep poking at the host. The device-cgroup confinement commit tells you exactly which device access they were worried about [inspired by google/gvisor].
- Hunt the unborn HEAD symref class across git tooling -- the CVE-2026-113408 primitive (protocol-v2 smart-HTTP symref -> path escape outside .git) likely lives in every git client and wrapper that trusts server-advertised symrefs: libgit2, git2go, dulwich, JGit, and CI checkout actions. Stand up the loopback harness and replay it against each [inspired by xssdoctor/git-cve-2026-113408-poc].
- Turn CSP allowlists into your recon list -- take @albinowax's method: enumerate script-src/connect-src allowlisted domains on bug-bounty targets, then fingerprint each for JSONP endpoints, upload paths, or open redirects. Any gadget converts a 'blocked' XSS into credential theft and a paid report [inspired by James Kettle / @albinowax].
- Fuzz Brotli's error-path dictionary state machine -- the 6a14c079 fix means serialized parse failures previously dropped shared-dictionary state; craft streams that fail mid-parse then resume, and race the newly-mutexed BrotliInputStream under thread contention to see if the lock covers every state transition. Sibling decoders (the C brotli, zlib-ng, zstd dictionaries) deserve the same treatment [inspired by google/brotli].
- Point vdet at silent patch streams, then weaponize -- run
vdetagainst high-value repos (gVisor, ANGLE, Dawn, XNNPACK) to catch fixes landed without CVEs, then diff the fix commit backward to reconstruct the bug and build a PoC before the advisory drops [inspired by vitorfhc/vdet]. - Sweep the 497 WordPress vulns for unpatched duplicates -- the Wordfence weekly dump is a target list: cross-reference the 312 plugins against live installs, then grep closed-source premium plugins for the same helper-function patterns (SQL concatenation, unserialized input, missing capability checks) that produced this week's batch [inspired by Ram Gall / Wordfence].
- Chase label-name escaping fixes in API client wrappers -- go-github just fixed label-name escaping in URL paths; the same class of bug (unencoded user-controlled strings in REST path segments) likely survives in every generated API client and internal tooling that interpolates repo/label/org names. Grep for
fmt.Sprintf+ URL joins [inspired by google/go-github]. - Recreate stale GPU texture IDs in sibling backends -- ANGLE now recreates texture IDs before glTexStorage; grep the Vulkan and Metal backends, plus Dawn's texture-import paths, for the unpatched twin and hammer teardown order under thread contention [inspired by google/angle].
.-. .-. (: `---------------------' :) ) github brief // #13 ( (: .---------------------. :) `-' `-'
Quiet stretch on the news wires, which left plenty of room to watch what people were actually pushing to git at 2 AM. Two threads ran through the diff stream: Google's sandbox and GPU maintainers quietly bolting locks onto container, decoder, and sanitizer state, and @xssdoctor shipping a seven-repo controlled experiment matrix against Muse's package-install and repo-import behavior -- every fixture deliberately inert, marker-file oracles only, no network, no subprocess, no symlinks. That's textbook harness discipline: prove what a build system executes behind closed doors without shipping anything a blue team could call a weapon. No conferenceware, no hype -- just clean oracles and suspect patch diffs worth pulling tonight.
- xssdoctor/muse-dependency-lifecycle-parent/leaf-20261114 -- parent package pins a researcher-owned dependency at a fixed commit with zero hooks of its own; the leaf's postinstall writes a marker strictly inside its own package dir. Together they answer whether Muse executes transitive lifecycle scripts from a pinned dep. No network, no payload, clean oracle.
- xssdoctor/muse-root-lifecycle-control-20261114 -- root-package control where
bun installwrites a marker and the build refuses to proceed without it, making root lifecycle execution directly observable. Simple, tight design. - xssdoctor/muse-git-nested-config-bypass-20261114 -- minimal nested repo-shaped directory at
vendor/lib, no scripts or symlinks, built purely to exercise nested Git config handling in a sanitizer. If Muse's import honors config from a nested repo, this fixture will show it. - xssdoctor/muse-benign-submodule-parent/leaf-20261114 -- submodule pair testing whether repo import recurses into submodule fetches; leaf is non-executable, one exported literal, no package metadata. Confirms fetch behavior without execution side effects.
- google/gvisor -- cgroup fixes, missing filestore cleanup, and explicit device-cgroup confinement of the sandbox (heads e45d53c7, ab5f509c). The exact commit shape that closes -- or accidentally opens -- container-escape and fd-leak surface. Pull it before the CVE does.