.-. .-. (: `--------------------' :) ) intel brief // #17 ( (: .--------------------. :) `-' `-'
- 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 a filestore handle open across container teardown and keep poking at the host from a half-dead sandbox. Worth a 10-minute diff [google/gvisor].
- 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), letting branch-update resolution write outside the repository directory. Clean, inert oracle you can run locally in five minutes [@xssdoctor]. - CSP allowlists turned into credential exfil pipes -- @albinowax showed that an allowlisted host 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 just a pre-approved exfil list [James Kettle / @albinowax].
- WordPress upgrade-window RCE under active probing -- CVE-2026-119977 is an unauthenticated race condition in the core update process hitting versions 4.7 through 7.1.3, fixed in 7.1.4 plus backports, with exploitation attempts already observed post-release. Unauthenticated -> RCE in core means patch tonight, not this quarter [Ram Gall / Wordfence].
- HTTP header injection escalated to desync in one prompt -- Kettle demonstrates that a single-prompt escalation chain turns header injection into CRLF-powered request smuggling, serving random users a redirect to a collaborator host. PortSwigger bolted a scan check onto Burp; go re-scan your old 'low severity' header-injection findings before someone else does [James Kettle / @albinowax].
- SVG sanitizers bypassed via response headers alone -- six of eight popular SVG sanitizers fell, with Firefox executing JavaScript triggered purely by response headers on a benign XML body. 'Sanitize the markup' is dead as a strategy; the delivery context is the bug [James Kettle / @albinowax].
- Brotli shared-dictionary state loss on serialized parse failure -- commit 6a14c079 fixes a decoder that drops dictionary state when a serialized parse fails, plus mutex synchronization bolted onto BrotliInputStream for concurrent decompression. Given CVE-2026-111497 (HTTP2Shell) already proved Brotli bugs go critical, diff this one hard [google/brotli].
- 497 WordPress plugin vulns in one week -- 497 vulnerabilities across 312 plugins and one theme from 218 researchers in a single week, on top of 549 the week before. Plugin disclosure volume is a firehose; treat it as a target-selection catalog, not a reading list [Ram Gall / Wordfence].
.-. .-. (: `----------------------' :) ) possibilities // #17 ( (: .----------------------. :) `-' `-'
- Diff gVisor's filestore teardown for held-handle escapes -- Pull heads e45d53c7 and ab5f509c, trace which filestore cleanup path was missing, and try to hold a descriptor open across sandbox teardown from inside a half-dead container; then check whether the new device-cgroup confinement actually blocks /dev access or just narrows it [inspired by google/gvisor].
- Replay the unborn HEAD symref against other git clients -- The CVE-2026-113408 harness proves protocol-v2 smart-HTTP can smuggle a symref that escapes
.git; point the same loopback fixture at libgit2, JGit, dulwich, and go-git clients plus CI checkout actions to find who else resolves branch updates outside the repo dir [inspired by xssdoctor/muse-repo-import-control-20261114]. - Fuzz Brotli serialized-parse failure paths for dictionary-state corruption -- Commit 6a14c079 shows state loss on parse failure; build a fuzzer that interleaves failing serialized dictionaries with concurrent BrotliInputStream reads to hunt for use-after-reset or stale-window leaks, and check whether the C library shares the same reset bug the TypeScript bindings just fixed [inspired by google/brotli].
- Mine CSP allowlists for JSONP, upload, and redirect gadgets -- Take Kettle's Blind Trust methodology to your bug bounty targets: enumerate script-src allowlisted hosts, probe each for JSONP endpoints, open redirects, or upload paths, and chain any reflected XSS into credential theft that the policy itself pre-approves [inspired by portswigger.net].
- Race the WordPress core update window on unpatched hosts -- CVE-2026-119977 is an unauthenticated race in the update process; if you hold a sanctioned target, instrument the upgrade-window timing on 4.7-7.1.3 to understand the race primitive, and check whether backported fixes introduced a second, narrower window [inspired by wordfence.com].
- Hunt SVG upload endpoints that trust body sanitization -- Apply Scalable Vector Grief: find targets that sanitize SVG markup but serve uploads with attacker-influenced response headers, then test Firefox's header-triggered execution to bypass the sanitizer entirely [inspired by portswigger.net].
- Re-test every parked header-injection finding for desync -- Kettle's one-prompt escalation means yesterday's 'informational' CRLF/header-injection reports on proxies and caches are now critical; re-probe them for request smuggling and victim-redirect chains before the queue gets crowded [inspired by portswigger.net].
- Recreate the Muse lifecycle matrix against other repo-import sandboxes -- @xssdoctor's parent/leaf dependency, root postinstall, submodule recursion, and nested-config fixtures are a reusable battery; clone the matrix and point it at any service that imports user repos and runs installs to map which lifecycle scripts actually execute [inspired by xssdoctor/muse-dependency-lifecycle-parent-20261114].
.-. .-. (: `---------------------' :) ) github brief // #17 ( (: .---------------------. :) `-' `-'
Quiet stretch on the news side for whole days at a time, which left plenty of room to watch what people were actually pushing to git at 2 AM. Two threads ran through the diff stream: @xssdoctor dropped a seven-repo controlled experiment matrix in a single day probing Muse's repo-import and package-install behavior -- transitive lifecycle execution from a pinned dependency, root-package postinstall, submodule recursion, nested Git config handling, and an inert import control, every fixture deliberately non-malicious with marker-file oracles only -- while Google's firehose touched the container/GPU/compiler sandbox layer everything else trusts: gVisor confining itself to a device cgroup, Brotli fixing dictionary-state loss, ANGLE and Dawn both churning texture-handle code. No conferenceware, no hype -- just clean harnesses and suspect patch diffs worth pulling tonight.
- xssdoctor/muse-dependency-lifecycle-parent-20261114 -- Parent JS package ships zero pre/install/postinstall hooks but pins a researcher-owned dependency at a fixed commit, testing whether Muse's install still executes transitive lifecycle code. Clean, inert oracle for install-script execution [@xssdoctor].
- xssdoctor/muse-dependency-lifecycle-leaf-20261114 -- Companion leaf whose postinstall writes a marker strictly inside its own package dir -- no network, no subprocess, no symlink. The detectable payload half of the lifecycle probe; grab both repos together [@xssdoctor].
- xssdoctor/muse-git-nested-config-bypass-20261114 -- Minimal nested repo-shaped directory at vendor/lib with no scripts, symlinks, or network, built to exercise nested Git config handling in a sanitizer. Zero payload, pure config-parsing stress -- the exact shape that historically smuggles config escapes [@xssdoctor].
- xssdoctor/muse-root-lifecycle-control-20261114 -- Inert control asking whether Muse's build runs a root-package lifecycle script after inspecting the Git tree; bun install writes a marker and the build refuses to proceed without it, making script execution observable. Textbook control design [@xssdoctor].
- google/gvisor -- Cgroup fixes, missing filestore cleanup, and explicit device-cgroup confinement landed across heads e45d53c7 and ab5f509c with zero bulletin noise. Silent hardening of a container-escape surface is the loudest signal on the wire this month [google/gvisor].