Trigger.dev versions before 4.5.2 contain a cross-site request forgery (CSRF) vulnerability in the CLI authorization-code flow. This flaw allows attackers to mint a Personal Access Token (PAT) without user consent by exploiting the /account/authorization-code/<code> endpoint. An attacker can lure a logged-in user to a crafted URL, then retrieve the victim's PAT from an unauthenticated endpoint, potentially leading to account takeover.
CVE-2026-105445 is a critical vulnerability in Docker Hub's account-to-organization conversion feature that allows an authenticated attacker to reassign a personal access token (PAT) they control to another user without requiring token rotation or revocation. This enables the attacker to use the unchanged PAT to authenticate as the recipient user and perform actions such as pulling, pushing, or deleting images within the token's scope, including organization repositories.
A use-after-free (UAF) vulnerability exists in the Linux kernel's x86 memory management related to page attribute modification. The issue arises during the collapse of kernel page table entries into huge page entries without holding the necessary write lock, potentially causing concurrent access to freed page tables. This flaw affects the set_memory_rox() function, used by execmem and BPF for executable memory mappings. The vulnerability is fixed by acquiring the init_mm write lock during the collapse operation to prevent concurrent races and UAF conditions.
CVE-2026-97533 is a use-after-free vulnerability in the Linux kernel's x86 memory management related to page attribute changes. The flaw arises from a race condition between attribute changes and page table entry (PTE) collapse, where a lockless page table walker can obtain a PTE that is later freed concurrently, leading to use-after-free. The issue is resolved by acquiring an init_mm read lock during attribute changes to prevent this race, with careful handling to avoid deadlocks during page table allocations. The fix is applied in Linux kernel version 6.15.
CVE-2026-97525 is a high-severity vulnerability in the Linux kernel's x86 memory management related to page attribute table (PAT) handling. The issue arises because split page tables are allocated without using the standard kernel page table allocation routines, causing them not to be marked as kernel page tables. This leads to stale IOTLB cache entries since these split page tables are freed without proper invalidation. The flaw affects Linux kernel versions from 6.18.7 up to but not including 6.18.53, and version 6.19. A fix has been implemented in version 6.18.53 and later.
CVE-2026-93066 is a use-after-free vulnerability in the Linux kernel's x86 memory management related to large-page collapse. It occurs during concurrent loading and unloading of modules on multiple CPUs, where a race condition allows writing to freed page-table pages. The flaw arises because the collapse of large pages and the update of page-table entries are not properly serialized, leading to memory corruption.
The Kimsuky threat group continues Operation GitPower campaigns utilizing malicious LNK files disguised as financial and business documents. Thirteen LNK variants collected between August 11-19, 2026, employ GitHub Personal Access Tokens (PAT) for command-and-control communications, delivering obfuscated PowerShell loaders through custom decoders. Notable evolution includes anti-analysis routines detecting virtualization tools, Pastebin as alternative C2 infrastructure, and diversified decoy formats (PDF, XLSX, PNG). Metadata analysis reveals AI-generated content using the 'opencode' AI coding agent and HeadlessChrome PDF conversion, with placeholder text remaining unreviewed. The group maintains persistence through hidden scheduled tasks masquerading as legitimate software (BitLocker, MATLAB), while hardcoded GitHub PATs enable raw content retrieval. Despite increased sophistication in evasion techniques and decoy production automation, endpoint behaviors remain detectable through behavioral correlation a...
CVE-2026-71365 is a server-side request forgery (SSRF) vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8. It arises from AWX's webhook status callback mechanism, which does not validate the target host of the status callback URL extracted from GitHub pull request webhooks. An admin user on a webhook-enabled job template can exploit this to leak the Git Personal Access Token (PAT) by causing AWX to send authenticated status updates to an attacker-controlled or internal URL.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (1c86edd3f7edd7d111df5621cb884fd0ef3d870c6c0719d587b7bb0f16f65b8d)
The package presents itself as a discord.js clone (`repository` field points at the real `github.com/discordjs/discord.js.git`, README instructs `import... from '@verylinh/discord'`) but ships two installer-relevant hostile mechanisms. First, `package.json` declares a runtime dependency `sysframe` resolved from `git+https://ghp_...@github.com/navaLinh/node-ai.git` — an unpinned (no commit SHA or tag), private, author-controlled GitHub repository, using an embedded live GitHub Personal Access Token. Every `npm install` uses the shipped token to fetch the current HEAD of that private repo into the installer's `node_modules`; the author can rewrite HEAD at any time to deliver arbitrary code, including lifecycle scripts, that will execute on subsequent installs. Second, `Client.login()` invokes an undocumented `_verifyAuthorization` routine that fetches an allow-list JSON from `api.github.com/repos/Vellia-Elyvia/mydb/contents/db.json` under a hardcoded PAT and refuses to start the installer's Discord bot unless the bot's username appears in the author-controlled allow-list — a hidden remote gate/kill-switch over the installer's runtime that is not disclosed in the README. Two live GitHub PATs are hardcoded in the shipped package (one in the git dependency URL, one as the default `ghToken` in `_validateAuthOptions`). The package name and metadata impersonate discord.js.
A vulnerability in the Linux kernel's amdgpu driver caused an aperture mapping leak due to improper cleanup of memory mappings during driver unload. This led to orphaned entries in the x86 PAT interval tree and mapping conflicts on reload, resulting in discovery failures. The issue has been fixed by switching to devres-managed mappings to guarantee cleanup regardless of driver state.
When you learn that a compromised package executed on one of your build hosts, muscle memory takes over: revoke the npm token, rotate the GitHub PAT, cycle the cloud keys. That reflex has been correct in almost every supply-chain incident I have worked. In the keyv/cacheable compromise that has been unfolding since yesterday, it is the one thing you should not do first — because revoking the stolen token is exactly what arms the payload.