. . . t h e d e a d . d o g . . .
.-----------..__ .-----------------------. __..---------._ .-.
| .---------. \/ \/ .+*+. . |
| : A `--.._ . _..--' : |
| : . /:\ : |
| : /:\ ./:::\. : |
| : (_:_) .:/::|::\:. : /
\ : _|_ .::/:::|:::\::. .<
> . .:::/::::|::::\:::. : \
/ : .:::/::::--+--::::\:::. : |
| : .:::::/:::::::|:::::::\:::::. : |
| : .::::::/\:::::::.:.:::::::/\::::::. : |
| : .:::::::/ \[0xDEAD:0xBEEF]/ \:::::::. : |
| : .::::::::/ /\ \::::..:..::::/ /\ \::::::::. : |
| : .::::::::/ / \ \:::: : ::::/ / \ \::::::::. : |
| : (::::::::/_ tDd _\:::'.:.`:::/_ PWN _\::::::::) : |
| : (:::::::::| ``::::'' .:. ``::::'' |:::::::::) : |
| : (:::::::::| .:::::::.. ..:::::::. |:::::::::) : |
| : (:::::::::|:::::' [ x ] [ x ] `:::::|:::::::::) : |
| : (:::::::::\:::::. `---' `---' .:::::/:::::::::) : |
\ : (::::::::::\ `:::. .:::. .:::' /::::::::::) : |
> . \:::::::::::\__ ::. / /|\ \ .:: __/:::::::::::/ : |
/ : \::::::::::::| :::. \_|_/ .::: |::::::::::::/ : /
| : \:::::::::::| ::::_|||||_:::: |:::::::::::/ .<
| : \::::::::::/\ .:/\_/|\_/\:. /\::::::::::/ : \
| : `::::::::' ``::.| | |.::'' `::::::::' : |
| : `-----' 8===8`:::'8===8 `-----' : |
| : _\_/:::::\_/_ : |
| : /___/:::::\___\ `|' : |
| : `===============' (`:') : |
| : \:/ : |
| : .+*+. . . :: [ t D d : A C E ] :: . . ' : |
| :.. : A ..: |
| `---.._ `--..___..--~`\.-------------------./'~--..___..--' . |
`-------`~--..___ `' `' ___..--~--' '
_______________________/ - x live: off x - \_______________________
/`-----------------------'\
/\___/\ (: `_____________________' :) /\___/\
/ .:::. \ / [ tDd // THE DEAD DOG ] \ / .:::. \
/[ x x ]\ / .:: MMXXVI A.D. ::. \ /[ x x ]\
\ \V_V/ / / LATRANDO, VULNERA INVENIO \ \ \V_V/ /
`-(U)-' (_=================================_) `-(U)-'
.-. .-. (: `---------------------------------' :) ) the rabbit hole // today // 24h ( (: .---------------------------------. :) `-' `-'
openclaw's Hook Chains and Keycloak's Loose Tokens
TL;DR: openclaw shipped a pile of auth and code-exec fixes -- repo-configured git hooks and fsmonitor pinning being the loudest -- while Keycloak patched authorization codes that weren't cryptographically bound to clients, letting attackers redeem codes across clients.
Nothing fresh landed inside this exact clock window, so we're working the latest dispatches off the patch-watch feeds -- and the backlog is fat. The nastiest of the lot is openclaw running git against untrusted checkouts without pinning core.hooksPath/core.fsmonitor, so a malicious repo points fsmonitor at an arbitrary binary and the Gateway executes it during session-diff baselines -- the fix exports gitEnvironment() and forces -c overrides (issue 661). The same hook-smuggling class shows up in worktree create/remove/restore/GC ops, where repo-configured post-checkout hooks handed arbitrary code execution to any repo owner the service touches (issue 651). Beyond code exec, the isolation story is grim: role-required sandboxes were scoped per agent instead of per authenticated principal, so guests sharing an agent shared a container and could read each other's files -- the patch keys the sandbox by principal and drops rw to ro (issue 669), and child agents ignored the parent's permission policy entirely, running with defaults until the fix propagated sessionPermissionPolicy down (issue 662). Add a Gateway-confusion bug where wake messages for finished subagents dispatched through the most recently activated Gateway -- a rival Gateway hijacks the completion and rips the victim's data into the attacker's session (issue 663) -- and openclaw's async message bus reads like a checklist of TOCTOU sins: membership checked before queueing but never revalidated after admission (issue 673), session ownership resolved at broadcast time instead of enqueue time (issue 658), and file-transfer approvals remembered by requested path rather than canonical path, so a symlink swap redirects later transfers (issue 667).
Keycloak's side is smaller but sharper. CVE-2026-16089 is the headliner: authorization codes carried no cryptographic client binding, so an attacker alters the embedded client UUID and redeems the code for another client -- patch stores and verifies the UUID server-side (issue 666). GroupPolicyProvider matched a bare token group name like 'Admins' against any allowed group regardless of hierarchy, a textbook name-vs-ID confusion now fixed by resolving bare names to top-level groups and comparing IDs (issue 668). The OIDCRedirectUriBuilder left reserved OIDC params in client-supplied redirect_uri query/fragment, letting wildcard redirects inject duplicate code/state/id_token and confuse first-param clients (issue 665), and the JWT Authorization Grant skipped consent checks entirely -- 'consent required' clients could grab scopes the user never approved until verifyConsentStillAvailable got bolted into the grant flow (issue 664). Grafana rounds it out with CVE-2026-17033: LibraryPanel PATCH mutated the folder UID in place before authorization, letting a read-only user on the source folder smuggle a panel into a folder they control -- the fix deep-copies before UpdatedObject (issue 676). Classic mutate-then-authorize. Worth a 10-minute diff against your own PATCH handlers.
.-. .-. (: `-------------------------------------' :) ) bookmarked feeds // the rabbit hole ( (: .-------------------------------------. :) `-' `-'
| Bookmarked Feed | Focus / Notes | Site | RSS Feed |
|---|---|---|---|
| Vulnerability Spoiler Alert | Pre-CVE Open-Source Security Patch Early Warning (Security Patch Commit Analysis RSS) | https://vulnerabilityspoileralert.com/ | https://vulnerabilityspoileralert.com/feed.xml |